README file for net-snmp Version: 5.9

DISCLAIMER

  The Authors assume no responsibility for damage or loss of system
  performance as a direct or indirect result of the use of this
  software.  This software is provided "as is" without express or
  implied warranty.

TABLE OF CONTENTS

  Disclaimer
  Table Of Contents
  Introduction
* Supported Architectures
  Availability
  Web Page
* Installation
  Copying And Copyrights
* Frequently Asked Questions
  Helping Out
* Code Update Announcements
* Mailing Lists
  Agent Extensibility
  Example Agent Configuration and Usage
  Configuration
  Submitting Bug Reports
  Closing
  Thanks

  * = Required Reading.

INTRODUCTION

  This package was originally based on the CMU 2.1.2.1 snmp code.  It
  has been greatly modified, restructured, enhanced and fixed.  It
  hardly looks the same as anything that CMU has ever released.  It
  was renamed from cmu-snmp to ucd-snmp in 1995 and later renamed from
  ucd-snmp to net-snmp in November 2000.

  This README file serves as a starting place to learn about the
  package, but very little of the documentation is contained within
  this file.  The FAQ is an excellent place to start as well.
  Additionally, there are a bunch of README files for specific
  architectures and specific features.  You might wish to look at some
  of these other files as well.

SUPPORTED ARCHITECTURES

  Please see the FAQ for this information.

  Please let us know if you compile it on other OS versions and it
  works for you so we can add them to the above list.

  Porting:  Please! read the PORTING file.

  Also note that many architecture have architecture specific README
  files, so you should check to see if there is one appropriate to
  your platform.

AVAILABILITY

  Download:
    - http://www.net-snmp.org/download/
  Web page:
    - http://www.net-snmp.org/
  Project Wiki:
    - http://www.net-snmp.org/wiki/
  Sourceforge Project page:
    - http://sourceforge.net/projects/net-snmp

  The old ucd-snmp.ucdavis.edu web site and ftp server is now
  offline and should not be accessed any longer.

WEB PAGES

  http://www.net-snmp.org/
  http://sourceforge.net/projects/net-snmp
  http://www.net-snmp.org/wiki/

INSTALLATION

  See the INSTALL file distributed with this package.

COPYING AND COPYRIGHTS

  See the COPYING file distributed with this package.

FREQUENTLY ASKED QUESTIONS

  See the FAQ file distributed with this package.
  This is also available on the project Wiki at

     http://www.net-snmp.org/wiki/index.php/FAQ

  so that the wider Net-SNMP community can help maintain it!

HELPING OUT

  This is a project worked on by people around the net.  We'd love
  your help, but please read the PORTING file first.  Also, subscribe
  to the net-snmp-coders list described below and mention what you're
  going to work on to make sure no one else is already doing so!
  You'll also need to keep up to date with the latest code snap shot,
  which can be obtained from CVS using the information found at
  http://www.net-snmp.org/cvs/.

  Contributions to the Net-SNMP source code in any form are greatly
  appreciated.  We expect the parties providing such contributions to
  have the right to contribute them to the Net-SNMP project or that
  the parties that do have the right have directed the person
  submitting the contribution to do so.  In addition, all contributors
  need to be aware that if the contribution is accepted and
  incorporated into the Net-SNMP project, it will be redistributed
  under the terms of the license agreement used for the entire body of
  work that comprises the Net-SNMP project (see the COPYING file for
  details).  If this license agreement ever changes the contribution
  will continue to be released under any new licenses as well.  Thank
  you, in advance, for your gracious contributions.

CODE UPDATE ANNOUNCEMENTS

  See the NEWS file and the ChangeLog file for details on what has
  changed between releases.

  We hate broadcasting announce messages to other mailing lists and
  newsgroups, so there is a mailing list set up to handle release
  announcements.  Any time we put new software out for ftp, we'll mail
  this fact to net-snmp-announce@lists.sourceforge.net.  See the
  MAILING LISTS section described below to sign up for these
  announcements.

  We will post new announcements on a very infrequent basis to the
  other channels (the other snmp mailing lists and newsgroups like
  comp.protocols.snmp), but only for major code revisions and not for
  bug-fix patches or small feature upgrades.

MAILING LISTS

  The lists:

    A number of mailing lists have been created for support of the project:
    The main ones are:

      net-snmp-announce@lists.sourceforge.net  -- For official announcements
      net-snmp-users@lists.sourceforge.net     -- For usage discussions
      net-snmp-coders@lists.sourceforge.net    -- For development discussions

    The -coders list is intended for discussion on development of code
    that will be shipped as part of the package.  The -users list is
    for general discussion on configuring and using the package,
    including issues with coding user-developed applications (clients,
    managers, MIB modules, etc).

    Please do *NOT* send messages to both -users and -coders lists.
    This is completely unnecessary, and simply serves to further
    overload (and annoy) the core development team.   If in doubt,
    just use the -users list.


    The other lists of possible interest are:

      net-snmp-cvs@lists.sourceforge.net       -- For cvs update announcements
      net-snmp-bugs@lists.sourceforge.net      -- For Bug database update announcements
      net-snmp-patches@lists.sourceforge.net   -- For Patch database update announcements

    Please do NOT post messages to these lists (or to the announce list above).
    Bug reports and Patches should be submitted via the Source Forge tracker
    system.  See the main project web pages for details.

    To subscribe to any of these lists, please see:

      http://www.net-snmp.org/lists/


  Archives:
    The archives for these mailing lists can be found by following links at

      http://www.net-snmp.org/lists/

AGENT EXTENSIBILITY

  The agent that comes with this package is extensible through use of
  shell scripts and other methods.  See the configuration manual pages
  (like snmpd.conf) and run the snmpconf perl script for further details.

  You can also extend the agent by writing C code directly.  The agent
  is extremely modular in nature and you need only create new files,
  re-run configure and re-compile (or link against its libraries).  No
  modification of the distributed source files are necessary.  See the
  following files for details on how to go about this:
  http://www.net-snmp.org/tutorial-5/toolkit/,
  agent/mibgroup/examples/*.c

  Also, see the local/mib2c program and its README file for help in
  turning a textual mib description into a C code template.

  We now support AgentX for subagent extensibility.  The net-snmp
  agent can run as both a master agent and a subagent.  Additionally,
  a toolkit is provided that enables users of it to easily embed a
  agentx client into external applications.  See the tutorial at
  http://www.net-snmp.org/tutorial-5/toolkit/ for an example of how
  go about doing this.

CONFIGURATION

  See the man/snmp.conf.5 manual page.

  For the agent, additionally see the man/snmpd.conf.5 manual page.

  For the snmptrapd, see the man/snmptrapd.conf.5 manual page.

  You can also run the snmpconf perl script to help you create some of
  these files.

SUBMITTING BUG REPORTS

  Important: *Please* include what version of the net-snmp (or
  ucd-snmp) package you are using and what architecture(s) you're
  using, as well as detailed information about exactly what is wrong.

  To submit a bug report, please use the web interface at
  http://www.net-snmp.org/bugs/.  It is a full-fledged
  bug-tracking system that will allow you to search for already
  existing bug reports as well as track the status of your report as
  it is processed by the core developers.

  If you intend to submit a patch as well, please read the PORTING
  file before you do so and then submit it to
  http://www.net-snmp.org/patches/.

CLOSING

  We love patches.  Send some to us!  But before you do, please see
  the 'PORTING' file for information on helping us out with the
  process of integrating your patches (regardless of whether its a new
  feature implementation or a new port).

  Also, We're interested if anyone actually uses/likes/hates/whatever
  this package...  Mail us a note and let us know what you think of it!

  Have fun and may it make your life easier,

    The net-snmp developers

THANKS

  This project has been graciously supported by a long list of people
  (too long to keep roperly up to date).  To them we owe our deepest
  thanks (and you do too!).  Please see the git log or ChangeLog file,
  where the core developers are careful to have (hopefully always)
  pointed out where patches have come from.

The following is a list of SNMP MIB tables and object, and their
implementation status for Net-SNMP.

Note that simply adding a MIB file does not allow the agent to return values
for the MIB. See the FAQ question here for details:

   http://www.net-snmp.org/FAQ.html#How_do_I_add_a_MIB_to_the_agent_


This table was generated by inspecting the source, so it may be incorrect,
especially with regards to OS platform support. If an object/table is listed
for your OS but doesn't work (or vice-cersa), let us know.

The Rel column indicates the first release that an object/table was
available. That does not imply that  all platforms indicated in the OS
column were supported for that release. There is no breakdown of feature
introduction by platform. Note that the earliest CVS information I could
find was for sometime around ucd-snmp 3.2.

The OS platform is probably the least reliable of the columns, as most are
marked as 'unix?', indicating that most unix-based platforms should
support the table.

An '=' in a file path indicates that the table/object name should be
substituted in place of the '=' in the path. All paths are relative to
the agent/mibgroup directory.

X.*.0 indicates all scalars under node X.
X.?.0 indicates all scalars execept as noted.
.Y.0 indicates that Y is an exception to the previous scalar group.


Table Style
----------------------------
  O  old (ucd) style helper
  D  table data helper
  I  table iterator
  A  iterate_access
  S  scalar helper
  G  scalar group helper
  W  watched scalar
  M  mfd
  C  container table

Platform Keys
------------------
A All systems
U unix based
   L Linux
   S Solaris
   H HP-UX
   B BSD Based
     F FreeBSD
     O OpenBSD
     N NetBSD
     X MacOSX
W Win32 based
  $ Microsoft
  C cygwi---
  M MingW

A number after a platform indicates notes at the bottom of the file.

 table/object group           OS       Rel   Styl File
==============================================================================
SNMPv2-MIB
 system.?.0                   A         5.5     W mibII/system_mib.c
 .sysORLastChange.0           A         5.5     W mibII/sysORTable.c
 sysORTable                   A         5.5     C mibII/sysORTable.c
 snmp.*.0                     A         5.5     G mibII/snmp_mib.c
 setSerialNo.0                A         5.0     W mibII/setSerialNo.c

------------------------------------------------------------------------------
SNMP-FRAMEWORK-MIB
 snmpEngine.*.0               A         ~4.0?   O snmpv3/snmpEngine.c

------------------------------------------------------------------------------
SNMP-MPD-MIB
 snmpMPDStats.*.0             A         ~4.0?   G snmpv3/snmpMPDStats.c

------------------------------------------------------------------------------
SNMP-TARGET-MIB
 snmpTargetSpinLock.0         A         3.6     O target/snmpTargetAddrEntry.c
 snmpTargetAddrTable          A         3.6     O target/snmpTargetAddrEntry.c
 snmpTargetParamsTable        A         3.6     O target/snmpTargetParamsEntry.c
 snmpUnavailableContexts.0    A         5.5     G target/target_counters.c
 snmpUnknownContexts.0        A         5.5     G target/target_counters.c

------------------------------------------------------------------------------
SNMP-NOTIFICATION-MIB
 snmpNotifyTable              A         4.2     O notification/=
 snmpNotifyFilterProfileTable A         4.2     O notification/=
 snmpNotifyFilterTable        A         4.2     O notification/=
 nlmConfig.*.0                ---
 nlmStats.*.0                 ---

------------------------------------------------------------------------------
NOTIFICATION-LOG-MIB
 *                            ---

------------------------------------------------------------------------------
SNMP-PROXY-MIB
 snmpProxyTable               ---

------------------------------------------------------------------------------
SNMP-USER-BASED-SM-MIB
 usmStats.*.0                 A         ~4.0    O --- deleted ---
 usmStats.*.0                 A         5.5     G snmpv3/usmStats.c
 usmUserTable                 A         ~4.0?   O snmpv3/usmUser.c

------------------------------------------------------------------------------
SNMP-VIEW-BASED-ACM-MIB
 vacmContextTable             A         ~3.5    I mibII/vacm_context.c
 vacmSecurityToGroupTable     A         ~3.5    O
 vacmAccessContextTable       A         ~3.5    O mibII/vacm_vars.c
 vacmViewSpinLock.0           A         ~3.5    O
 vacmViewTreeFamilyTable      A         ~3.5    O

------------------------------------------------------------------------------
SNMP-USM-DH-OBJECTS-MIB
 usmDHPublicObjects.*.0       A         5.2     S snmp-usm-dh-objects-mib/=/*
 usmDHUserKeyTable            A         5.2     M snmp-usm-dh-objects-mib/=/*
 usmDHKickstartTable          ---

------------------------------------------------------------------------------
SNMP-COMMUNITY-MIB
 snmpCommunityMIBObjects.*.0  ---
 snmpCommunityTable           ---
 snmpTargetAddrExtTable       ---

------------------------------------------------------------------------------
IF-MIB
 ifNumber.0                   U $2      ~3.2    O mibII/interfaces.c
 ifTableLastChange.0          ---
 ifTable (old)                U $2      ~3.5    O mibII/interfaces.c
 ifTable (new)                L         5.2     M if-mib/ifTable/*
 ifTable (new)                 FOS      5.4     M if-mib/ifTable/*
 ifXTable                     L         5.2     M if-mib/ifXTable/*
 ifXTable                      FOS      5.4     M if-mib/ifXTable/*
 ifStackLastChange.0          ---
 ifStackTable                 ---
 ifTestTable                  ---
 ifRcvAddressTable            ---

------------------------------------------------------------------------------
RFC1213-MIB
 atTable (D)                  U $2      ~3.5    O mibII/at.c
 egp.*.0                      ---
 egpNeighTable                ---

------------------------------------------------------------------------------
IP-MIB
 ip.*.0                       U $2      ~3.2    G mibII/ip.c
 icmp.*.0                     U $2      ~3.2    G mibII/icmp.c

 ipSystemStatsTable           L         5.2     M ip-mib/=/*
 ipSystemStatsTable            S        5.5     M ip-mib/=/*
 ipIfStatsTableLastChange.0   ---
 ipIfStatsTable               L--       5.5     M ip-mib/=/*

 ipAddrTable (D)              U $2      4.2     O mibII/ipAddr.c
 ipAddressSpinLock.0          A         5.5     O mibII/ipAddr.c
 ipAddressTable               L         5.2     M ip-mib/=/*
 ipAddressTable                S        5.5     M ip-mib/=/*
 ipAddressPrefixTable         L         5.3     M ip-mib/=/*

 ipRouteTable (D)             U $2      ~3.5    O mibII/*route*.c
 ipNetToMediaTable (D)        U $2      ~3.5    O mibII/at.c
 ipNetToPhysicalTable         (implemented as inetNetToMediaTable)
 inetNetToMediaTable          L         5.2     M ip-mib/=/*
 ipDefaultRouterTable         L         5.5     M ip-mib/=/*

 icmpStatsTable               ---
 icmpMsgStatsTable            ---

 ipv4InterfaceTableLastChange ---
 ipv4InterfaceTable           L          5.3    M ip-mib/=/*

 ipv6InterfaceTableLastChange ---
 ipv6InterfaceTable           L          5.3    M ip-mib/=/*
 ipv6RouterAdvertTable        ---
 ipv6IpForwarding.0           L          5.3    S ip-mib/ip_scalars.c
 ipv6IpDefaultHopLimit.0      L          5.3    S ip-mib/ip_scalars.c
 ipv6RouterAdvertSpinLock.0   ---
 ipv6ScopeZoneIndexTable      ---

 ipForwarding.0               L          5.4    S ip-mib/ip_scalars.c
 ipDefaultTTL.0               L          5.4    S ip-mib/ip_scalars.c

------------------------------------------------------------------------------
IPV6-MIB
 ipv6MIBObjects.?.0           U         4.1     O mibII/ipv6.c
 .ipv6IfTableLastChange.0     ---
 .ipv6RouteNumber.0           ---
 .ipv6DiscardedRoutes.0       ---
 ipv6Interfaces               U1        4.1     O mibII/ipv6.c
 ipv6IfTable                  U1        4.1     O mibII/ipv6.c
 ipv6IfStatsTable             U1        4.1     O mibII/ipv6.c
 ipv6AddrPrefixTable          ---
 ipv6AddrTable                ---
 ipv6RouteTable               ---
 ipv6NetToMediaTable          ---

------------------------------------------------------------------------------
IPV6-TCP-MIB
 ipv6TcpConnTable             U1        4.1     O mibII/ipv6.c

------------------------------------------------------------------------------
IPV6-UDP-MIB
 ipv6UdpTable                 U1        4.1     O mibII/ipv6.c

------------------------------------------------------------------------------
IPV6-ICMP-MIB
 ipv6IfIcmpTable              U1        4.1     O mibII/ipv6.c

------------------------------------------------------------------------------
IP-FORWARD-MIB
 ipForward.*.0                ---
 ipForwardTable (D)           ---
 ipCidrRouteTable (D)(new)    L         5.2     A mibII/=
 ipCidrRouteTable (D)(newer)  L         5.2     M ip-forward-mib/=/*
 inetCidrRouteTable           L         5.2     M ip-forward-mib/=/*

------------------------------------------------------------------------------
TCP-MIB
 tcp.*.0                      U $2      ~3.2    G mibII/tcp.c
 tcpConnTable (D)             U $2      4.2     I mibII/tcpTable.c
 tcpConnectionTable           L         5.3     M tcp-mib/=/*
 tcpConnectionTable            S        5.4     M tcp-mib/=/*
 tcpListenerTable             L         5.3     M tcp-mib/=/*
 tcpListenerTable              S        5.4     M tcp-mib/=/*

------------------------------------------------------------------------------
UDP-MIB
 udpEndpointTable             L         5.3     M udp-mib/=/*
 udpEndpointTable              S        5.4     M udp-mib/=/*
 udp.*.0                      U $2      ~3.2    G mibII/udp.c
 udpTable (D)                 U $2      4.2     I mibII/udpTable.c

------------------------------------------------------------------------------
IF-INVERTED-STACK-MIB
 *                           ---

------------------------------------------------------------------------------
RMON-MIB
 etherStatsTable              U         5.0     O Rmon/statistics.c
 .etherStatsJabbers           L3        5.5     M rmon-mib/=/*
 etherHistoryControlTable     U         5.0     O Rmon/history.c
 etherHistoryTable            U         5.0     O Rmon/history.c
 alarmTable                   U         3.2     O Rmon/alarm.c
 eventTable                   U         3.2     O Rmon/event.c
 logTable                     U         5.0     O Rmon/event.c
 hostControlTable             ---
 hostTable                    ---
 hostTimeTable                ---
 hostTopNControlTable         ---
 hostTopNTable                ---
 matrixControlTable           ---
 matrixSDTable                ---
 matrixDSTable                ---
 filterTable                  ---
 channelTable                 ---
 bufferControlTable           ---
 captureBufferTable           ---

------------------------------------------------------------------------------
HOST-RESOURCES-MIB
 hrSystem.*.0                 U         ~3.3    O host/hr_system.c
 hrMemorySize                 U         ~3.3    O host/hr_storage.c
 hrStorageTable               U         ~3.3    O host/hr_storage.c
 hrDeviceTable                U         ~3.3    O host/hr_device.c
 hrProcessorTable             U         ~3.3    O host/hr_proc.c
 hrNetworkTable               U         ~3.3    O host/hr_network.c
 hrPrinterTable               U         ~3.3    O host/hr_print.c
 hrDiskStorageTable           U         ~3.3    O host/hr_disk.c
 hrPartitionTable             U         ~3.3    O host/hr_partition.c
 hrFSTable                    U         ~3.3    O host/hr_filesys.c
 hrSWOSIndex.0                ---       ~3.3    O host/hr_swrun.c
 hrSWRunTable                 U         ~3.3    O host/hr_swrun.c
 hrSWRunPerfTable             U         ~3.3    O host/hr_swrun.c
 hrSWInstalled.*.0            U         ~3.3    O host/hr_swinst.c
 hrSWInstalledTable           U         ~3.3    O host/hr_swinst.c

------------------------------------------------------------------------------
DISMAN-EVENT-MIB
 mteTriggerTable              A         5.0     O disman/=
 mteTriggerFailures.0         ---
 mteTriggerDeltaTable         A         5.0     O disman/=
 mteTriggerExistenceTable     A         5.0     O disman/=
 mteTriggerBooleanTable       A         5.0     O disman/=
 mteTriggerThresholdTable     A         5.0     O disman/=
 mteObjectsTable              A         5.0     O disman/=
 mteEventTable                A         5.0.7   D disman/=
 mteEventFailures.0           ---
 mteEventNotificationTable    A         5.0.7   D disman/=
 mteResource.*.0              ---
 mteEventSetTabel             ---

------------------------------------------------------------------------------
DISMAN-SCHEDULE-MIB
 schedLocalTime.0             A         5.3     D disman/schedule/=
 schedTable                   A         5.3     D disman/schedule/=

------------------------------------------------------------------------------
DISMAN-EXPRESSION-MIB (expired ID)
 expErrorTable                U         5.2     O disman/expression/=
 expExpressionTable           U         5.2     O disman/expression/=
 expObjectTable               U         5.2     O disman/expression/=
 expValueTable                U         5.2     O disman/expression/=

------------------------------------------------------------------------------
DISMAN-PING-MIB (draft-ietf-disman-remops-mib-v2*)
 pingCtlTable                 U         5.2     O disman/ping/=
 pingProbeHistoryTable        U         5.2     O disman/ping/=
 pingResultsTable             U         5.2     O disman/ping/=

------------------------------------------------------------------------------
DISMAN-TRACEROUTE-MIB (draft-ietf-disman-remops-mib-v2*)
 traceRouteCtlTable           U         5.2     O disman/traceroute/=
 traceRouteHopsTable          U         5.2     O disman/traceroute/=
 traceRouteProbeHistory       U         5.2     O disman/traceroute/=
 traceRouteResultsTable       U         5.2     O disman/traceroute/=

------------------------------------------------------------------------------
DISMAN-NSLOOKUP-MIB (draft-ietf-disman-remops-mib-v2*)
 lookupCtlTable               U         5.2     O disman/nslookup/=
 lookupResultsTable           U         5.2     O disman/nslookup/=

------------------------------------------------------------------------------
DISMAN-SCRIPT-MIB
 *                            ---

------------------------------------------------------------------------------
EtherLike-MIB
 dot3StatsTable               L        5.5      M etherlike-mib/=

------------------------------------------------------------------------------
AGENTX-MIB
 *                            ---

------------------------------------------------------------------------------
LM-SENSORS-MIB
 lmTempSensorsTable           LS        5.0     O ucd-snmp/lmSensors.c
 lmFanSensorsTable            LS        5.0     O ucd-snmp/lmSensors.c
 lmVoltSensorsTable           LS        5.0     O ucd-snmp/lmSensors.c
 lmMiscSensorsTable           LS        5.0     O ucd-snmp/lmSensors.c

------------------------------------------------------------------------------
UCD-SNMP-MIB
 prTable                      U $       ~3.2    O ucd-snmp/proc.c
 memory.*.0                   U         ~3.2    O ucd-snmp/memory*.c
 extTable                     U $       ~3.2    D ucd-snmp/extensible.c
 dskTable                     U         3.2     O ucd-snmp/disk.c
 fileTable                    A         3.6     O ucd-snmp/file.c
 laTable                      U $       ~3.2    O ucd-snmp/loadave.c
 systemStats.*.0              U         3.4     O ucd-snmp/vmstat*.c
 ipFwAccTable                 U         3.5     O misc/ipfwacc.c
 dlModTable                   U         4.2     O ucd-snmp/dlmod.c
 diskIOTable                  U         4.1     O ucd-snmp/diskio.c
 ucdDemoMIBObjects            A         ~3.5    O examples/ucdDemoPublic.c
 logMatch                     U         ~3.5    O ucd-snmp/logmatch.c
 version.*.0                  A         ~3.2    O ucd-snmp/versioninfo.c
 snmperrs.*.0                 A         ~3.5    O ucd-snmp/errormib.c
 mrTable (D)                  ---

------------------------------------------------------------------------------
NET-SNMP-EXTEND-MIB
 nsExtendConfigTable          U         ~3.5    D agent/extend.c
 nsExtendOutput1Table         U         ~3.5    D agent/extend.c
 nsExtentOutput2Table         U         ~3.5    D agent/extend.c

------------------------------------------------------------------------------
NET-SNMP-AGENT-MIB
 nsModuleTable                A         5.0     I agent/nsModuleTable.c
 nsCacheTable                 A         5.0     I agent/nsCache.c
 nsConfigDebug.*.0            A         5.0     I agent/nsDebug.c
 nsDebugTokenTable            A         5.0     O
 nsConfigLogging              A         5.0     I agent/nsLogging.c
 nsLoggingTable               A         5.0     O
 nsTransactionTable           A         5.0     I agent/nsTransactionTable.c
 netSnmpExampleScalars        A         5.0     O
 netSnmpIETFWGTable           A         5.0     D examples/data_set.c
 netSnmpHostsTable            A         5.0     A examples/=*
 nstAgentModules              A         5.0     O

------------------------------------------------------------------------------
NET-SNMP-VACM-MIB
 nsVacmAccessTable            A         5.4     I agent/nsVacmAccessTable.c

------------------------------------------------------------------------------
MTA-MIB
 mtaTable                     U         4.2     O mibII/mta_sendmail.c
 mtaGroupTable                U         4.2     O mibII/mta_sendmail.c

------------------------------------------------------------------------------
SMUX-MIB
 smuxPeerTable                ---
 smuxTreeTable                ---

------------------------------------------------------------------------------
BGP4-MIB (draft-ietf-idr-bgp4-mib)
 bgpPeerTable                 A         3.5     O smux/snmp_bgp.c

------------------------------------------------------------------------------
OSPF-MIB (draft-ietf-ospf-mib-update)
 *                            A         3.5     O smux/snmp_ospf.c

------------------------------------------------------------------------------
RIPv2-MIB
 *                            A         3.5     O smux/snmp_rip2.c

------------------------------------------------------------------------------
TUNNEL-MIB
 tunnelIfTable                L         4.2     O tunnel/tunnel.c
 tunnelConfigTable            L         4.2     O tunnel/tunnel.c
 tunnelInetConfigTable        ---

------------------------------------------------------------------------------
SCTP-MIB
 sctpStats                    L         5.5     S sctp-mib/sctpScalars*
 sctpParameters               L         5.5     S sctp-mib/sctpScalars*
 sctpAssocTable               L         5.5     C sctp-mib/=
 sctpAssocLocalAddrTable      L         5.5     C sctp-mib/=
 sctpAssocRemAddrTable        L         5.5     C sctp-mib/=
 sctpLookupLocalPortTable     L         5.5     C sctp-mib/=
 sctpLookupRemPortTable       L         5.5     C sctp-mib/=
 sctpLookupRemHostNameTable   L         5.5     C sctp-mib/=
 sctpLookupRemPrimIPAddrTable L         5.5     C sctp-mib/=
 sctpLookupRemIPAddrTable     L         5.5     C sctp-mib/=

------------------------------------------------------------------------------
SNMP-TSM-MIB
 snmpTsmStats                 A         5.6     D tsm-mib/snmpTsmStats/=
 snmpConfiguration            A         5.6     W tsm-mib/=

------------------------------------------------------------------------------
TLSTM-MIB
 snmpTlstmSession             A         5.6     W tlstm-mib/=/*
 tlstmCertificateMapping.*    A         5.6     w tlstm-mib/=
 tlstmCertToTSNTable          A         5.6     D tlstm-mib/=/*
 tlstmParamsTable             A         5.6     D tlstm-mib/=/*
 tlstmAddrTable               A         5.6     D tlstm-mib/=/*

==============================================================================

Misc notes
----------
 1: available for systems using KAME ipv6
 2: with platform SDK. See README.win32
 3: works only with Intel and Broadcom network cards and must run as root only

Other feature info
------------------
 smux                                     3.2
 AgentX                                   4.0
 proxy support                            4.2
 override token                           5.0
 proper context support                   5.2
 DISMAN-EVENT-MIB implementation rewrite  5.3
 AgentX, host, disman/event by default    5.3
 SSH Transport module                     5.5
 (D)TLS Transport module                  5.6

  Net-SNMP contains a reasonably full implementation of the AgentX agent
extensibility protocol (RFC 2741) in as much as it supports all
the protocol operations described in this document.  The core
functionality has received a reasonable amount of exposure, and
is believed to be more or less stable in normal use.   It will
also handle the non-graceful termination of subagents - returning
a 'genErr' error for three successive requests before unregistering
the unresponsive subagent.

  A subagent will attempts to re-establish contact with a dead and
resurrected master based on the agentxPingInterval setting. The default
for this configuration variable is 15 seconds. It can be changed by
putting the following line in your APPLICATION.conf file:

                agentxPingInterval 60

will make the subagent try to ping the master every 60 seconds, and if
the connection is deemed broken it'll try and reconnect to the master
agent after that point (once every 60 seconds).

  Similarly, a subagent will not be able to re-register in place of a
defunct colleague until the master agent has received three requests
for the dead connection (and hence unregistered it).

  Some of the less frequently used features (index allocation,
range registration, etc), have received less thorough testing,
and may well not be fully functional.   Some of the omissions
of the earlier release (use of GetBulk, the AgentX MIB)
are still missing from this version.

  AgentX support is now included in the agent by default, but needs
to be explicitly enabled before use.  Activate it using by putting a line

		master	agentx

in the snmpd.conf file.  This support is also enabled automatically
when the '-x' flag is given (to specify a different master AgentX socket),
or when the agent is invoked as an AgentX subagent (i.e. via the name
'agentxd' or with the '-X' flag).

  See the main project web page for an examples of a simple stand-alone
subagent.  (http://www.net-snmp.org/tutorial/tutorial-5/toolkit/)


  Please report any problems experienced to the net-snmp-coders list.

Dave

Some notes for the AIX port
===========================

1. Known problems
-----------------

There are the following known problems on AIX:

1) Shared libraries / embedded perl

Up to (and including) net-snmp 5.4, configure forced a static build
on AIX which caused embedded Perl to be disabled as well.

Starting with net-snmp 5.4.1, we build shared libraries by default on AIX
(like on any other platform) using run-time linking. configure forces the
use of the required "-brtl" linker flag.

With net-snmp 5.5 the shared library build is broken again but the there is
no forced static build - use --disable-shared when building.

2) "grep: capacity exceeded" or "sed: Command line is too long" during configure

The version of "grep" shipped with AIX versions up to (and including) 5.1
has a known limitation of only supporting a maximum of 2048 characters per line.
This may cause a significant number of "grep: capacity exceeded" errors during
configure which breaks the build. See bug 1367794 for details. The fix is to
either install GNU grep (and have it in PATH before the AIX grep) or to upgrade
to AIX 5.2 or later.

There's a similar issue with AIX /usr/bin/sed up to at least AIX 5.3 that
causes a significant number of "sed: Command line is too long." errors during
configure. The fix is to install GNU sed.

3) nlist errors with 64-bit kernels

Accessing certain MIB objects on AIX 5.x machines running a 64-bit kernel will
trigger nlist/klookup errors. Starting from net-snmp 5.4, you can avoid those
by using

   ./configure --without-kmem-usage ...


4) IPv6

Starting with net-snmp 5.4 you can enable the UDPIPv6 and TCPIPv6 transports
on AIX 5.x:

   ./configure --enable-ipv6

There's no support for the IPv6 MIBs, though.

5) Compiler for Perl

In general, Perl modules need to be compiled with the same compiler and
compiler options as Perl itself. configure detects some mismatches (gcc vs.
vendor compiler), but treats different incarnations of the same compiler type
as similar. If your version of Perl (e.g. the one supplied by IBM for AIX 5.x)
has been compiled with cc_r on AIX, please make sure you also use CC=cc_r when
building net-snmp. Building with xlc in this case is known to fail (see bug
#1600099).


2. Patches
----------

You may want to have a look for existing AIX patches in our patches tracker
(http://www.net-snmp.org/patches/). If you can offer patches yourself to
improve the AIX support, please submit them there.


3. Feedback
-----------

Please also see README and PORTING.

If you have questions, additional insights or (even better) patches regarding
net-snmp on AIX, please refer to the net-snmp mailing lists (see
http://www.net-snmp.org/lists).

Some notes for the HP-UX 11.0/11i port
======================================

1. Starting the net-snmp daemon via rc script
---------------------------------------------

When starting the net-snmp daemon via rc script you have to trap some signals
because otherwise the daemon will die the moment the rc script ends. I trap
the signals 1, 2 and 3 via "trap '' 1 2 3" immediately before starting the
daemon. I didn't check whether all these signals need to be trapped, probably
SIGHUP will suffice. BTW this applies to the HP-UX 10.x version as well. It
would be a good idea to ignore or handle these signals in the daemon...

2. Author, credits, comments
----------------------------

The HP-UX 11.0 port was done by Johannes Schmidt-Fischer <jsf@InterFace-AG.com>

If you have questions or problems please feel free to contact me via the
above mentioned e-mail address. Please send a copy of your e-mail to the
net-snmp-coders mailing list - probably someone else can answer your
question earlier than me;-)

Some notes for the IRIX port
============================

1. Compiling
------------

net-snmp 5.3.1 and later have been compiled successfully on IRIX 6.5 using the
MIPSpro C compiler 7.4.4m in C99 mode:

	CC=c99 ./configure && make && make install

Please note that the "host" module doesn't compile on IRIX, so you *cannot*
configure with "--with-mib-modules=host".

Compiling with gcc may be possible, but is unsupported at this point in time
due to difficulties with the IRIX system headers. Brent Bice has reported
a successful build of net-snmp 5.4 with gcc 3.4.6 on a IP30 machine using:

	CFLAGS="-D_PAGESZ=16384 -D_MIPS3_ADDRSPACE -DIP30 -DR10000 -DMP \
	        -DCELL_PREPARE -DBHV_PREPARE" ./configure ...

See http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi/0620/bks/\
SGI_Developer/books/DevDriver_PG/sgi_html/ch10.html and
/var/sysgen/Makefile.kernio .

2. CPU stats
------------

net-snmp 5.4.1 and later reports CPU statistics on IRIX 6.x by default using
the hardware/cpu/cpu_sysinfo module. There's also an alternative implementation:
hardware/cpu/cpu_pcp. For full discussion and build instructions for cpu_pcp
see Patch #1675869:

  http://sf.net/support/tracker.php?aid=1675869


3. Known Issues
---------------

Accessing certain MIB objects on IRIX64 machines (i.e. when running a 64-bit
kernel will trigger nlist/klookup errors. The agent will not return proper
values for the affected MIB objects (e.g. tcpConnTable, udpTable).
Starting from net-snmp 5.4, you can avoid nlist altogether (recommended for
IRIX64) by using

   ./configure --without-kmem-usage ...


3. Feedback
-----------

Please also see README and PORTING.

If you have questions, additional insights or (even better) patches regarding
net-snmp on IRIX, please refer to the net-snmp mailing lists (see
http://www.net-snmp.org/lists).

This version of net-snmp supports an experimental SNMPv3 security model
using Kerberos 5 for authentication.  The protocol is described in an
up-and-coming IETF Internet-Draft.

This document describes a brief overview of the Kerberos Security Model
and how to use it.

DESCRIPTION:

The Kerberos Security Model does not use USM; it is completely seperate
and is not tied to USM in any way.  It works by placing the following
ASN.1 sequence inside of the SNMPv3 msgSecurityParameters:

ksmSecurityParameters ::= SEQUENCE {
-- The Kerberos 5 checksum type used to checksum this message
    ksmChecksumType		INTEGER(0..2147483647),
-- The actual keyed checksum data returned by Kerberos
    ksmChecksum			OCTET STRING,
-- The Kerberos 5 message (either an AP_REQ or AP_REP)
    ksmKerberosMsg		OCTET STRING,
-- The cached ticket identifier
    ksmCachedTicket		INTEGER(0..2147483647)
}

Note that the whole SEQUENCE is BER encoded as an OCTET STRING.

ksmChecksumType is an integer which corresponded to the checksum algorithm
used to secure this message as defined by Kerberos (see section 8.3 of
RFC1510).

ksmChecksum is the output of the checksum algoritm defined by ksmChecksumtype
(with all NULs in the space for the checksum).

ksmKerberosMsg is a Kerberos 5 AP_REQ or AP_REP message, depending on
whether or not it is a request or a response (AP_REQ for requests, AP_REP
for responses).

ksmCachedTicket is a integer which uniquely identifies a ticked already
cached on the agent to save the overhead of transferring a whole AP_REQ/AP_REP.
If there is no such cached ticket, it is left at zero.

An agent, upon receiving a message using the KSM, will decode the AP_REQ
contained within the security parameters and thus validate the client's
identity.  Using the subkey contained within the AP_REQ, the agent will
validate the checksum (after first clearing the checksum bytes to zero),
and issue a response, encoding the appropriate AP_REP message in the
ksmSecurityParameters.

If the securityLevel of the message is set to AuthPriv, the scopedPdu
payload will be encrypted using the encryption key and algorithm of the
AP_REQ subkey.  Note that in this case, the msgData will be a BER-encoded
OCTET STRING corresponding to the "cipher" element of the EncryptedData
sequence defined in RFC 1510, section 6.1.

Since this security model is experimental, the number assigned to this
security model is taken from the recommendations of RFC 2271, section 5,
which specify enterprise-specific Security Models of the form:

	SnmpSecurityModel = enterpriseID * 256 + security model number
						 in that enterprise ID;

In the case of KSM this gives us:

	SnmpSecurityModel = 8072 * 256 + 0 = 2066432


USAGE:

To actually USE the Kerberos Security Model, do the following:

0) Install Kerberos

   Let it be stated up front - Installing Kerberos completely "cold", without
   any Kerberos experience at all, can be daunting (to say the least).  If you
   already have a Kerberos infrastructure at your site, then all of the hard
   work has been done.  If you do NOT, but you still want to tackle it,
   you might be interested in the Kerberos FAQ, which can be found at:

   http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html

   Currently the code in net-snmp only supports using MIT Kerberos
   libraries to link against (you should be able to use any kind of Kerberos
   server, however).

1) Compile net-snmp with Kerberos.

   This assumes that you already have Kerberos libraries in place.

   Configure net-snmp to include the Kerberos Security Model (ksm) and
   use --with-cflags and --with-ldflags to specify the location and names
   of Kerberos header files and libraries.  For example, on my system I
   run:

   ./configure --with-cflags='-I/usr/krb5/include' \
      --with-ldflags='-L/usr/krb5/lib -lkrb5 -lcrypto -lcom_err -R/usr/krb5/lib'

   Note that this is on Solaris, and that -R is required to set the correct
   shared library path.  If you have a newer version of Kerberos, you might
   instead have to use:

   -lkrb5 -lk5crypto -lcom_err

   as the libraries to link against.  If you get errors (for example, you
   get a message that says the compiler isn't working) you can check
   config.log for the output of the compiler.

2) Configure Kerberos and SNMP

   Currently, net-snmp uses the "host" principal assigned to a host.  This
   may change in the future.  You will want to create host principals of
   the form:

   host/f.q.d.n@YOUR.REALM

   For example:

   host/mydesktop.example.org@EXAMPLE.ORG

   and place the encryption keys for these principals on every machine you
   wish to run a SNMP agent (you place each key on it's corresponding machine).
   Your Kerberos documentation should explain how to do this (in the case
   of MIT Kerberos, you want to look at the "ktadd" command inside of
   kadmin).

   If you have a Kerberos infrastructure, you likely already have these
   principals in place on your systems.

   If you're installing Kerberos for the first time as well, you also
   need to create client principals corresponding to your userid.  See
   your Kerberos documentation.

   On the SNMP _agent_ side, you'll want to place in your snmpd.conf file
   (the one that lives in /usr/local/share/snmp/snmpd.conf, or whereever
   you have configured on your system):

   rwuser -s ksm userid@YOUR.REALM

   to allow the Kerberos principal 'userid@YOUR.REALM' read/write access to
   the MIB tree.

3) Run the agent and client applications

   Note that before you do any of this, you will have to have valid Kerberos
   credentials (generally acquired with the "kinit" program).

   The agent should run without any additional flags.

   You should run the client apps with the following flags:

   -Y defSecurityModel=ksm
   -v 3
   -u username
   -l authNoPriv

   for example:

   snmpget -v 3 -Y defSecurityModel=ksm -u myname -l authNoPriv testhost \
						system.sysDescr.0

   If you wish to encrypt the payload, change the -l argument to "authPriv".

   If you run into problems, you can add the -Dksm flag to both the manager
   applications and the agent to get more detailed Kerberos error messages.
   Note that this setup assumes a working Kerberos infrastructure; if you
   run into problems, check to make sure Kerberos is working for you.

README.osX
$Id$

This is what I had to do to get it to work for me. Your mileage may vary.
If this doesn't work for you, or you have fixes for any problems listed,
please post to <net-snmp-coders@lists.sourceforge.net>. Thanks!

  - ALL

    - nlist doesn't support icmpstat

       - disable the icmp module during configure by specifying
         "--with-out-mib-modules=mibII/icmp", or at startup by adding
         "-I -icmp" to the snmpd command line.


  - 10.4.7 (Universal) and Leopard with 5.4 sources:
        [Supplied by Chris Jalbert]

       - build using gcc 4.0 (see below) and configure using:
                        --with-persistent-directory=/var/db/net-snmp \
                        --with-defaults \
                        --without-rpm \
                        --with-mib-modules="host ucd-snmp/diskio" \
                        --with-out-mib-modules="mibII/icmp host/hr_swrun" \
                        --without-kmem-usage

       The first line sets up persistent storage in the OS X standard location.

       The third line is necessary because RPM is not properly disabled.

       The fourth line includes those modules appear to build properly and
       mostly work. The next line is necessary because those sub-modules
       do not build.

       The final line is necessary because /dev/kmem was removed in
       the Intel / Universal builds of the OS, and I believe the APIs will
       be removed in Leopard.
         This line is the most critical for proper building on OS X.


  - 10.3.x and earlier

     - Some older versions of Apple's cpp doesn't like configure.

        - run 'gcc_select' to see what version you are using, and
          'gcc_select -l' to list available versions. I've had success with
          3.3, selected by running (as root) 'gcc_select 3.3'. (Note: this was
          on Panther, 10.3.2)

     - Some older versions of net-snmp as installed by Apple contains
       bad flags in net-snmp-config.

       - build your own version, and install over Apple's version. The
         configure flags you need for the same configuration:

         configure --prefix=/usr --mandir=/usr/share/man
                   --infodir=/usr/share/info --with-libwrap --with-defaults
                   --prefix=/usr --with-persistent-directory=/var/db/ucd-snmp
                   --with-mib-modules=host

README.snmpv3
-------------
How to setup SNMPv3, a very brief document for Dave to elaborate and
do a better job on since I suck at writing documentation and he
doesn't ;-) --Wes:

Note: SHA authentication and DES/AES encryption support is only available
if you have OpenSSL installed or if you've compiled using
--with-openssl=internal.  If you use --with-openssl=internal please
read the documentation in snmplib/openssl/README for important details.

Note: encryption support now *is* enabled in the binary releases downloadable
from the net-snmp web site.

Note: this description assumes you're using the software compiled from
source, and so installed using the default prefix location (/usr/local).
If you're working with a vendor-provided system, or have configured
things with a different prefix, you'll need to adjust locations accordingly.

CREATING THE FIRST USER:
------------------------
  First, you need to create a new snmpv3 user and give them rights to
  do things:

    net-snmp-config --create-snmpv3-user -a "my_password" myuser

  WARNING: SNMPv3 pass phrases must be at least 8 characters long!

  The above line creates the user "myuser" with a password of
  "my_password" (and uses MD5 and DES for protection).  (Note that
  encryption support isn't enabled in the binary releases downloadable
  from the net-snmp web site.)  net-snmp-config will also add a line
  to your snmpd.conf file to let that user have read/write access to
  your agent.  You may want to change this in your snmpd.conf file
  (see the snmpd.conf manual page).  Run net-snmp-config --help for
  more information about it.

  Start the agent and test your setup:
    /usr/local/sbin/snmpd
       [...wait a few seconds...  It will run in the background and
        return you to your shell immediately.]

    snmpget -v 3 -u myuser -l authNoPriv -a MD5 -A my_password localhost sysUpTime.0
       [ this should return information about how long your agent has been up]

    snmpget -v 3 -u myuser -l authPriv   -a MD5 -A my_password
                                         -x DES -X my_password localhost sysUpTime.0
       [ this should return similar information, but encrypts the transmission ]

CREATING A SECOND USER:
-----------------------
  Start the agent (if you didn't do so above).

  You can create as many users as you like using the above method, but
  this details another way of doing it while the agent is running by
  modifying the user database using the snmp protocol itself:

  Now, lets create a second user using the first user (just for fun)
  for both authentication purposes and as a template (or "cloning
  source"):

    snmpusm -v 3 -u myuser -l authNoPriv -a MD5 -A my_password localhost create wes myuser

  The above should have created the user "wes" with the same password as
  the "myuser" user.  So then, you need to change his password using:

    snmpusm -v 3 -u wes -l authNoPriv -a MD5 -A my_password localhost passwd my_password new_passphrase

  See, wasn't that easy?  You can now create users.  Wheeee....

  But, you'll have to add a configuration line that allows them access
  to do things.  Do this with another "rwuser" line in your
  /usr/local/share/snmp/snmpd.conf file (you'll need to stop and start
  the agent again, or send the agent a SIGHUP signal):

    rwuser wes

  Or, optional use the "rouser" token instead of the "rwuser" token to
  only grant them read-only access.

  Now, test your new user:

    snmpget -v 3 -u wes -l authNoPriv -a MD5 -A new_passphrase localhost sysUpTime.0


FURTHER STUDIES:
---------------

Tired of all those command line authentication options?
----------------------------------------
put something like this in your $HOME/.snmp/snmp.conf file (make it
readable only by you!!!):

  defSecurityName wes
  defContext ""
  defAuthType MD5
  defSecurityLevel authNoPriv
  defAuthPassphrase new_passphrase
  defVersion 3

And this is in place the last of the above example lines boils down to:

  snmpget localhost sysUpTime.0

Which is about as simple as I can make it for ya ;-)

README.solaris
$Id$

This document describes issues relating to compiling,
installing and using net-snmp on Solaris.

0.  Introduction
1.  Things you will need
2.  Disabling Sun's SNMP daemons
3.  Compiling net-snmp
4.  Obtaining and installing binaries
5.  Creating snmpd.conf and testing
6.  Creating your own binaries
7.  Using Sun's SNMP daemon and net-snmp together
8.  Monitoring disks, processes and execs (DISMAN-EVENT-MIB)
9.  Monitoring CPU temp, fan and power supply sensors (LM-SENSORS-MIB)
10.  MIB rewrites for IF-MIB, TCP-MIB and UDP-MIB

Additional compilation issues:

11.  Files descriptors and fopen
12.  Perl
13.  sed
14.  OpenSSL and crle
15.  IPv6
16.  Wish list

Other issues:

17.  Known Bugs!!
18.  Discussion and further information

------------------------------------------------------------

0.  Introduction

This document is a compilation of information relating to
running net-snmp (www.net-snmp.org) on Sun SPARC and Ultra
hardware under the Solaris operating system.

This can be done either in conjunction with or as a
replacement for Sun's SNMP daemons.

This is discussed in detail in the sections below.  Since
this is the work of several authors, credit is given.
Discussion, however, should take place on the net-snmp-users
or net-snmp-coders mailing lists so everybody can
benefit.  See http://sourceforge.net/mail/?group_id=12694 .
Use "net-snmp-users" for general usage questions and "net-snmp-coders" for
discussion of net-snmp source code.

No warranty is implied by this document.
This document is copyright but usage allowed under the same
licensing as net-snmp in general.  See http://www.net-snmp.org/COPYING.txt.

------------------------------------------------------------

1.  Things you will need

A.  Root access

Root access is required to follow pretty much any of
the steps below.  At a bare minimum, you will need
to be able to start and stop daemons, which requires root
(at least for the default ports).

B.  Determine existing SNMP functionality

SNMP uses ports 161 and 162 by default.  Only one application
can use them at a time.  If there is an existing SNMP
application (eg. Sun's snmpdx daemon) you need to either
turn this off or work around it.   You may also have
a previous version of net-snmp, the older ucd-snmp, or
something completely different.  The following commands:

   ps -ef | grep snm
   ps -ef | grep mibi

will give you a fairly good idea what is going on.

If you see something like:

  root 643 1 0 Jan 16 ? 5:49 /usr/local/sbin/snmpd

that's probably a version of net-snmp.  The instructions in various
sections below should give you clues on what to do next.

If you see something like:

  root 16178 1 0 13:16:04 pts/2 0:00 /usr/lib/snmp/snmpdx -y -c /etc/snmp/conf

and/or

  root 21371 1 0 Feb 07 ? 0:52 mibiisa -r -p 41178

then Sun's SNMP daemons are running.

If you need this, for example if you use the Solstice Enterprise
Agent, you may wish to run net-snmp as a sub-agent (see section 7).
Otherwise, you will need to disable Sun's daemons (see section 2).

Regardless you may wish to compile net-snmp from source
and install it (see sections 3, 5 and 6) or install
binaries (see sections 4 and 5).

If some other SNMP daemon is running, you will need to determine
where it came from and what it's being used for.  You get clues by
typing "snmpd -v" or "snmpd --help".  In some cases it may be
a subagent or agent from another application, such as ORACLE.  If
you disable its agent, you will need to re-create this functionality
under net-snmp (eg. by running it as a sub-agent).  ORACLE's SNMP
functionality is turned on by default and may be unnecessary if
you aren't using ORACLE's Enterprise Manager.  Refer to ORACLE's
documentation on how to disable it.


If you have decided to compile your own net-snmp, you will need ...

C.  A compilation environment

-a compiler (gcc or Sun's Forte cc) or the gcc libraries
   (note, the cc in /usr/ucb is NOT a full-blown compiler)
-OpenSSL (sunfreeware.com or source www.openssl.org)
-zlib (sunfreeware.com or source www.gzip.org/zlib/)
-an SNMP community string ("public" is deprecated)

If you are installing on a development machine, it may be best
to compile OpenSSL and zlib from source, otherwise
obtain the appropriate zlib for your platform from sunfreeware
and install (it goes to /usr/local automatically).
Obtain the appropriate OpenSSL for your platform from sunfreeware
and install (it goes to /usr/local), you may need the gcc libraries.
These libraries should not need to be installed if you are using
binaries, but your mileage may vary.  Note the library problem
with libcrypto noted below (section 14).

There are two choices for compilers.  Sun has a Forte development
suite that includes a standalone C compiler.  If you have it, it
is likely installed in /opt/SUNWspro/bin.

The more common choice is gcc (2.95.3 or better have been tested)
available from sunfreeware.com.  If you install gcc, you do not
need the gcc libraries.  3.3.2 or later is recommended.

Given that net-snmp is developed to work on a wide variety of
platforms, but especially for linux, there's a better chance of
it working using gcc at any given time. We also do regular test
builds with Sun cc, though.

 -- Bruce Shaw <Bruce.Shaw at shaw.ca>
 -- Thomas Anders <tanders@users.sourceforge.net>

------------------------------------------------------------

2.  Disabling Sun's SNMP daemons

Note:  Sun has started to include net-snmp (version 5.0.9 plus their
patches) with Solaris 10 and later.  These instructions are written
with Solaris 9 and previous in mind.

Out of the box, Sun runs four SNMP daemons: mibiisa, idmispd,
snmpXdmid and snmpdx.

These must be disabled before running net-snmp unless you are planning
on running them together (see Section 7 below).  Here is the procedure:

   cd /etc/rc3.d
   ./S76snmpdx stop
   ./S77dmi stop
   mv S76snmpdx s76snmpdx
   mv S77dmi s77dmi

If you are using Solstice Disksuite, you may also be running
mdlogd.  Leave this alone.

You will need to create a new script to start net-snmp.
See dist/snmpd-init.d and dist/snmptrapd-init.d for templates.

 -- Bruce Shaw <Bruce.Shaw at shaw.ca>

------------------------------------------------------------

3.  Compiling net-snmp

It is strongly recommended that you compile net-snmp from source.
That way you are guaranteed a working version for your specific
configuration of operating system, applications and libraries.

If, for some reason, you cannot compile on a specific machine,
there are binaries available for download (see section 4).
In addition, you may create your own binaries (see section 6).

You need to set your $PATH.  This is extremely important
because otherwise there may be conflicts between the various
components of the development environment.

If you are using FORTE:

PATH=/usr/bin:/usr/sbin:/usr/ccs/bin:/opt/SUNWspro/bin:/usr/local/bin:

If you are using gcc (installed in /usr/local/bin):

PATH=/usr/sbin:/usr/local/bin:/usr/ccs/bin:/usr/bin

Obtain a current version of net-snmp (which, if you're reading this,
presumably you have - don't you love recursion?) www.net-snmp.org/download/

Uncompress it and untar it in a working directory eg. /usr/local/src/net-snmp

In order to save a lot of typing, you should create a "configure"
script eg. bcc.sh in the directory below eg. /usr/local/src.

   ./configure --with-mib-modules="ucd-snmp/lmSensors ucd-snmp/diskio \
      smux mibII/mta_sendmail" --with-cc=gcc

(note, see the long discussion about Perl below)
(note, substitute "cc" for "gcc" as appropriate)
(note, for LM-SENSORS-MIB support, see discussion below)

then call this script from the net-snmp directory ie ../bcc.sh

and answer the appropriate questions (usually with the default).

When it completes, you should see something like:

---------------------------------------------------------
            Net-SNMP configuration summary:
---------------------------------------------------------

  Net-SNMP Version:           5.4
  Building for:               solaris2
  Network transport support:  Callback Unix TCP UDP
  SNMPv3 Security Modules:    usm
  Agent MIB code:             mibII ucd_snmp snmpv3mibs notification target
  \agent_mibs agentx agent_mibs utilities host disman/event-mib
  \ucd-snmp/diskio smux agentx mibII/mta_sendmail
  SNMP Perl modules:          disabled
  Embedded perl support:      disabled
  Authentication support:     MD5 SHA1
  Encryption support:         DES

Type:

   make

and watch for compile errors.

You will receive numerous warnings.  This is normal,
a side effect of supporting a variety of development environments.

Now type:

   make test

and watch for failures.  Also watch for the special tests for Solaris.

If you are satisfied with the tests, stop any snmpd daemons
that may be running (see section 2) and type:

   make install

When complete, go on to section 5 below.

 -- Bruce Shaw <Bruce.Shaw at shaw.ca>

------------------------------------------------------------

4.  Obtaining and installing binaries

It is strongly recommended that you compile net-snmp from source.
That way you are guaranteed a working version for your specific
configuration of operating system, applications and libraries.

Binaries for Solaris may be found in two locations.

www.sunfreeware.com - this installs as a package.
It does not have Perl support.

Therefore, I recommend:

   http://net-snmp.sourceforge.net/download/  (you will be redirected)

This is the official repository for binaries.

To determine which binary you need, you will need several pieces of
information.

-operating system version,
-hardware platform
-net-snmp version desired

The first two may be obtained by typing:

   uname -a

It will return something like:

SunOS foo 5.8 Generic_108528-14 sun4u sparc SUNW,Ultra-4

5.8 means Solaris 8
5.7 means Solaris 7  etc.

"sun4u" is the Ultra hardware platform
"sun4m" is SuperSPARC  eg. Sparc 5 or Sparc 10
"sun4d" is older SPARC boxes.

You can then decode the binary version by its name eg.:

net-snmp_5.0.9-SunOS_5.8_sun4u.tar.gz

means "net-snmp version 5.0.9 for Solaris 8 running on Ultra
hardware".

Once you have found the appropriate version, download it to a
distribution directory (making one if necessary) eg. /usr/local/dist

Type the following: (using the sample above)

   cd /
   tar -xvf /usr/local/dist/net-snmp-5.0.9-SunOS_5.8_sun4u.tar

The binaries, libraries, etc. will be installed in /usr/local.

Remove the tar file to save space.  Create an snmpd.conf (see below)
or use an existing one from another machine.
It installs in /usr/local/share/snmp.

Install a startup script (see section 1).

For further information, see README.solaris.binaries.x that ships
with the binaries.

--Bruce Shaw <Bruce.Shaw at shaw.ca>

------------------------------------------------------------

5.  Creating snmpd.conf and testing

When everything is installed, run:

   snmpconf -g basic_setup

and answer the questions appropriately.  If you are using
the defaults, place the resulting snmpd.conf file in:

/usr/local/share/snmp/snmpd.conf

A security note - use of the "public" community is deprecated.
This example uses "whatever" as a community.

When you have the daemon running either with the script above or running:

   /usr/local/sbin/snmpd

test the daemon's functionality by typing:

   snmpget -v 1 -c whatever localhost sysUpTime.0
   snmpwalk -v 2c -c whatever -m ALL localhost .1.3 | more

and paging through the results.

If you have problems, you can examine diagnostic messages
by running:

   /usr/local/sbin/snmpd -f -Le

or use gdb (available from www.sunsolve.com) as follows:

   cd /usr/local/sbin
   gdb snmpd
   run -f -Le

and when it blows up:

   bt

to get the backtrace.

You can use:

   run -f -Le -D <modulename>

to display debug messages.

To display all debug messages type:

   run -f -Le -D ALL

but this will be extremely verbose.

 -- Bruce Shaw <Bruce.Shaw at shaw.ca> with suggestions by Thushara Wickram

------------------------------------------------------------

6.  Creating your own binaries

Pick an appropriate name for a tarfile
eg. net-snmp-5.4.custom-SunOS_5.8_sun4u.tar (see above)
(this particular one means "a customized version of
net-snmp 5.4 that works under Solaris 8 running on Ultra hardware")

Create an empty directory such as /usr/local/dist, then do the following
from the source directory (using the example above):

   make install prefix=/usr/local/dist/usr/local \
        exec_prefix=/usr/local/dist/usr/local
   cd /usr/local/dist
   tar -cvf net-snmp-5.4.custom-SunOS_5.8_sun4u.tar usr

Transfer this file to the machine where you want to install from binary.
Place it in a distribution directory eg. /usr/local/dist
Type the following (using the example above):

   cd /
   tar -xvf /usr/local/dist/net-snmp-5.4.custom-SunOS_5.8_sun4u.tar

Remove the tar file to save space.  Create an snmpd.conf (see above)
or use an existing one from another machine.  If you are using
the defaults, it installs in /usr/local/share/snmp.  Install
a startup script (see section 2).

Note that if you create a binary with Perl support (see below) an
identically configured Perl needs to be installed as well.

 -- Bruce Shaw <Bruce.Shaw at shaw.ca>

------------------------------------------------------------

7.  Using Sun's SNMP daemon and net-snmp together

Net-SNMP may be used as a subagent in conjunction with Sun's snmpdx daemon.

To do this, you will need to modify several files,
all located in /etc/snmp/conf.

First, do the following:

   /etc/rc3.d/S76snmpdx stop (assuming you haven't done so already, and...)
   /etc/rc3.d/S77dmi stop    (...assuming you haven't renamed them)

   cd /etc/snmp/conf
   cp snmpd.conf snmpd.conf.orig
   cp snmpdx.acl snmpdx.acl.orig
   cp snmpdx.reg snmpdx.reg.orig
   cp snmpdx.rsrc snmpdx.rsrc.orig
   cp mibiisa.reg mibiisa.reg.orig
   cp mibiisa.rsrc mibiisa.rsrc.orig

modify snmpd.conf with the correct:

   sysdescr
   syscontact
   sysLocation
   system-group-read-community
   read-community (in my example below I will use community "whatever")
   trap
   trap-community
   managers (leave blank for all)

modify snmpdx.acl with the correct:

   trap-community
   trap-recipients
   communities
   access

Make sure that in snmpdx.reg the port is 161.

You will now need to add two files - net-snmp.reg and net-snmp.rsrc

In this example, "subtrees" is set for HOST-RESOURCES-MIB, and UCD-SNMP-MIB.
Do not use net-snmp's MIB-2 information as this is already provided by
Sun's mib and may cause a conflict.

::::: net-snmp.reg ::::::

# net-snmp.reg
# mib-2 is already provided by the mibiisa process
# that is a default sub agent of snmpdx
# we are specifying only hostmib and ucd
##########
# agents #
##########

# The following 3 macros are predefined:
#
#       mib-2      =    1.3.6.1.2.1
#       enterprise =    1.3.6.1.4.1
#       sun        =    1.3.6.1.4.1.42
#
# You can define your own macros, so that you can
# manipulate strings instead of OIDs in defining the agent.
# See the "agent" section below.

macros =
{
        host = mib-2.25
        ucd  = enterprise.2021
}

agents =
{
        {
                 name = "net-snmp"
                 subtrees = { host,ucd }
                 timeout = 2000000
                 watch-dog-time = 86400
        }
}

::::::::::::::::::

::::: net-snmp.rsrc ::::::

# /etc/snmp/conf/net-snmp.rsrc

resource =
{
        {
                registration_file = "/etc/snmp/conf/net-snmp.reg"
                policy = "spawn"
                type = "legacy"
                command = "/usr/local/sbin/snmpd $PORT"
      }

}

::::::::::::::::::

Stop any net-snmp processes that may be running.

Start Sun's daemons by typing:

   /etc/rc3.d/S76snmpdx start (assuming you haven't renamed it)
   /etc/rc3.d/S77dmi start    (assuming you haven't renamed it)

Wait a moment for everything to stabilize, then try these two queries:

   snmpget -v 1 -c whatever localhost sysDescr.0
   snmpget -v 1 -c whatever localhost hrSystemUptime.0

You should see something like:

   SNMPv2-MIB::sysDescr.0 = STRING: SunOS foo 5.6 Generic_105181-30 sun4u

which is Sun's daemon talking, and:

   HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (78540910) 9 days, 2:10:09.10

which is net-snmp talking.  It is acting as a sub-agent through Sun's daemon.

If Sun's daemons fail, you will need to shut down the snmpd daemons by typing:

   pkill snmpd

Then do the following:

   /etc/rc3.d/S76snmpdx stop  (assuming you haven't renamed it)
   /etc/rc3.d/S77dmi stop     (assuming you haven't renamed it)
   /etc/rc3.d/S76snmpdx start (assuming you haven't renamed it)
   /etc/rc3.d/S77dmi start    (assuming you haven't renamed it)

rather than trying to individually clobber all the various Sun daemons.

This configuration appears to deal properly with snmpgets
and handle mistakes gracefully.

Beyond this, your mileage may vary.

You may wish to modify the subtrees in net-snmp.reg as you find things
that do and don't work.  Remember to keep backup copies of working
configurations.

 -- Bruce Shaw <Bruce.Shaw at shaw.ca> from notes by Stefan Radman and C Wells

------------------------------------------------------------

8.  Monitoring disks, processes and execs (DISMAN-EVENT-MIB)

Important note: this section only applies to the old DISMAN-EVENT-MIB
implementation called "disman/event-mib", *not* the current "disman/event"
mib module which is active by default since net-snmp 5.3 and later.

For a full explanation of using DISMAN-EVENT-MIB, see:

http://www.net-snmp.org/man/snmpd.conf.html

To use this component, net-snmp must be compiled with the option..

--with-mib-modules="disman/event-mib"

This discussion concerns the use of DISMAN-EVENT-MIB with Solaris.

There is a bug preventing the use of some of its functionality.  This
discussion will document what is known to work and how to use it.

The problem revolves around the use of monitors.  The...

defaultMonitors yes

token will NOT work for reasons discussed below.  I suspect that the
notificationEvent tokens will not work for the same reason but this
has not been tested.  Your mileage may vary.  Same with includeAllDisks.

The documentation suggests using...

monitor -o prNames -o prErrMessage "process table" prErrorFlag != 0

to monitor all processes.  This will fail with ambiguous results.

To monitor processes, put a separate monitor line for each process.

For example:
######
proc smail
proc mdlogd

monitor -r 30 -i -o prNames.1 -o prErrMessage.1 "Process smail" prErrorFlag.1 !=0
monitor -r 30 -i -o prNames.2 -o prErrMessage.2 "Process Solstice Disksuite SNMP trap" prErrorFlag.2 !=0

To monitor disks, do the same.  An example:

########
# This example sends a trap if root has less than 10% available and /usr6 less t
han 90%
#
disk / 10%
disk /usr6 90%

monitor -i -r 30 -o dskPath.1 -o dskErrorMsg.1 "root file system" dskErrorFlag.1 !=0
monitor -i -r 30 -o dskPath.2 -o dskErrorMsg.2 "ORACLE file system" dskErrorFlag.2 != 0
#########

To implement an external program then monitor its results you need to set up your script.

Here is a sample script.

#!//usr/bin/ksh
xstatus=0

if [ $xstatus -eq 0 ];then
echo success: $0
else
echo FAILURE: $0
fi

exit $xstatus
###end of script tester##

Place this script in /usr/local/src and make it executable.  Make copies called
tester1, tester2 etc.
and make them executable.

Here is a sample snmpd.conf snippet that makes use of the exec feature:
##############

exec tester1 /usr/local/src/tester1
exec tester2 /usr/local/src/tester2
exec tester3 /usr/local/src/tester3
exec tester4 /usr/local/src/tester4
exec tester5 /usr/local/src/tester5

monitor -i -r 60 -o extNames.1 -o extOutput.1 "status table 1" extResult.1 != 0
monitor -i -r 60 -o extNames.2 -o extOutput.2 "status table 2" extResult.2 != 0
monitor -i -r 60 -o extNames.3 -o extOutput.3 "status table 3" extResult.3 != 0
monitor -i -r 60 -o extNames.4 -o extOutput.4 "status table 4" extResult.4 != 0
monitor -i -r 60 -o extNames.5 -o extOutput.5 "status table 5" extResult.5 != 0
##############

While snmpd is running, go to /usr/local/src and modify one of the tester programs eg. tester1

xstatus=1

and save the file.  Sometime in the next 60 seconds, a trap will be generated.
Change the value back to 0, then modify another file.

If you are unsure of the correct row number within a specific table, do an snmpwalk eg.

snmpwalk -v 2c -c public -m ALL localhost prNames

The same methodology can presumably be used for fileName and laNames.  Your mileage may vary.


 -- Bruce Shaw <Bruce.Shaw at shaw.ca>  with Allan McIntosh and Wes Hardaker

------------------------------------------------------------

9.  Monitoring CPU temp, fan and power supply sensors (LM-SENSORS-MIB)

Note: This module (ucd-snmp/lmSensors) works in "read only" mode to examine
sensors.  It cannot change switch or fan settings.

It has been tested at least on the following platforms:

Enterprise 450
V880
280R

If you have information about other platforms this is desperately needed.  For
example, the only "state" that I'm aware of for an i2c is "OK".  The more
information we have, the richer the components.

Please report any performance statistics, bugs or omissions to the users list.
Please report any code suggestions to the coders list.  See links below.


This component delivers information that you would normally see by typing:

/usr/platform/`uname -m`/sbin/prtdiag -v

At present this is only supported on the Ultra (sun4u) platform.

To display this information, net-snmp must be compiled with the option:

--with-mib-modules="ucd-snmp/lmSensors"

Early Ultra servers such as the Ultra 1 or Ultra 2 did not report
any sensor information at all.  Later servers, such as the Enterprise 450
reported this information using kstat.  Sun's latest servers make use
of the picld daemon to control system resources and report fan information.
This module reads in the information from picld.  It cannot modify settings.

You can see this information by typing:

prtpicl -v | more

The following is typical output from net-snmp:

E450# snmpwalk -v 2c -c public -m ALL localhost lmSensors
LM-SENSORS-MIB::lmTempSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmTempSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmTempSensorsIndex.3 = INTEGER: 2
LM-SENSORS-MIB::lmTempSensorsIndex.4 = INTEGER: 3
LM-SENSORS-MIB::lmTempSensorsDevice.1 = STRING: Ambient
LM-SENSORS-MIB::lmTempSensorsDevice.2 = STRING: CPU1
LM-SENSORS-MIB::lmTempSensorsDevice.3 = STRING: CPU2
LM-SENSORS-MIB::lmTempSensorsDevice.4 = STRING: CPU3
LM-SENSORS-MIB::lmTempSensorsValue.1 = Gauge32: 22
LM-SENSORS-MIB::lmTempSensorsValue.2 = Gauge32: 45
LM-SENSORS-MIB::lmTempSensorsValue.3 = Gauge32: 46
LM-SENSORS-MIB::lmTempSensorsValue.4 = Gauge32: 49
LM-SENSORS-MIB::lmFanSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmFanSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmFanSensorsIndex.3 = INTEGER: 2
LM-SENSORS-MIB::lmFanSensorsDevice.1 = STRING: fan type CPU number 0
LM-SENSORS-MIB::lmFanSensorsDevice.2 = STRING: fan type PWR number 0
LM-SENSORS-MIB::lmFanSensorsDevice.3 = STRING: fan type AFB number 0
LM-SENSORS-MIB::lmFanSensorsValue.1 = Gauge32: 33
LM-SENSORS-MIB::lmFanSensorsValue.2 = Gauge32: 31
LM-SENSORS-MIB::lmFanSensorsValue.3 = Gauge32: 63
LM-SENSORS-MIB::lmVoltSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmVoltSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmVoltSensorsIndex.3 = INTEGER: 2
LM-SENSORS-MIB::lmVoltSensorsDevice.1 = STRING: power supply 0
LM-SENSORS-MIB::lmVoltSensorsDevice.2 = STRING: power supply 1
LM-SENSORS-MIB::lmVoltSensorsDevice.3 = STRING: power supply 2
LM-SENSORS-MIB::lmVoltSensorsValue.1 = Gauge32: 38
LM-SENSORS-MIB::lmVoltSensorsValue.2 = Gauge32: 39
LM-SENSORS-MIB::lmVoltSensorsValue.3 = Gauge32: 39
LM-SENSORS-MIB::lmMiscSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmMiscSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmMiscSensorsIndex.3 = INTEGER: 2
LM-SENSORS-MIB::lmMiscSensorsDevice.1 = STRING: FSP
LM-SENSORS-MIB::lmMiscSensorsDevice.2 = STRING: Backplane4
LM-SENSORS-MIB::lmMiscSensorsDevice.3 = STRING: Backplane8
LM-SENSORS-MIB::lmMiscSensorsValue.1 = Gauge32: 192
LM-SENSORS-MIB::lmMiscSensorsValue.2 = Gauge32: 0
LM-SENSORS-MIB::lmMiscSensorsValue.3 = Gauge32: 0

V880# snmpwalk -v 2c -c public -m ALL localhost lmSensors
LM-SENSORS-MIB::lmTempSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmTempSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmTempSensorsIndex.3 = INTEGER: 2
LM-SENSORS-MIB::lmTempSensorsIndex.4 = INTEGER: 3
LM-SENSORS-MIB::lmTempSensorsIndex.5 = INTEGER: 4
LM-SENSORS-MIB::lmTempSensorsIndex.6 = INTEGER: 5
LM-SENSORS-MIB::lmTempSensorsIndex.7 = INTEGER: 6
LM-SENSORS-MIB::lmTempSensorsIndex.8 = INTEGER: 7
LM-SENSORS-MIB::lmTempSensorsIndex.9 = INTEGER: 8
LM-SENSORS-MIB::lmTempSensorsIndex.10 = INTEGER: 9
LM-SENSORS-MIB::lmTempSensorsDevice.1 = STRING: CPU0_DIE_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.2 = STRING: CPU2_DIE_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.3 = STRING: CPU1_DIE_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.4 = STRING: CPU3_DIE_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.5 = STRING: CPU4_DIE_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.6 = STRING: CPU6_DIE_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.7 = STRING: MB_AMB_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.8 = STRING: IOB_AMB_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.9 = STRING: DBP0_AMB_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsDevice.10 = STRING: DBP1_AMB_TEMPERATURE_SENSOR
LM-SENSORS-MIB::lmTempSensorsValue.1 = Gauge32: 71
LM-SENSORS-MIB::lmTempSensorsValue.2 = Gauge32: 60
LM-SENSORS-MIB::lmTempSensorsValue.3 = Gauge32: 66
LM-SENSORS-MIB::lmTempSensorsValue.4 = Gauge32: 59
LM-SENSORS-MIB::lmTempSensorsValue.5 = Gauge32: 65
LM-SENSORS-MIB::lmTempSensorsValue.6 = Gauge32: 69
LM-SENSORS-MIB::lmTempSensorsValue.7 = Gauge32: 28
LM-SENSORS-MIB::lmTempSensorsValue.8 = Gauge32: 25
LM-SENSORS-MIB::lmTempSensorsValue.9 = Gauge32: 25
LM-SENSORS-MIB::lmTempSensorsValue.10 = Gauge32: 24
LM-SENSORS-MIB::lmFanSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmFanSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmFanSensorsIndex.3 = INTEGER: 2
LM-SENSORS-MIB::lmFanSensorsIndex.4 = INTEGER: 3
LM-SENSORS-MIB::lmFanSensorsIndex.5 = INTEGER: 4
LM-SENSORS-MIB::lmFanSensorsIndex.6 = INTEGER: 5
LM-SENSORS-MIB::lmFanSensorsIndex.7 = INTEGER: 6
LM-SENSORS-MIB::lmFanSensorsIndex.8 = INTEGER: 7
LM-SENSORS-MIB::lmFanSensorsIndex.9 = INTEGER: 8
LM-SENSORS-MIB::lmFanSensorsIndex.10 = INTEGER: 9
LM-SENSORS-MIB::lmFanSensorsDevice.1 = STRING: CPU0_PFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.2 = STRING: CPU1_PFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.3 = STRING: CPU0_SFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.4 = STRING: CPU1_SFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.5 = STRING: IO_BRIDGE_PFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.6 = STRING: IO_BRIDGE_SFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.7 = STRING: IO0_PFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.8 = STRING: IO1_PFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.9 = STRING: IO0_SFAN_TACH
LM-SENSORS-MIB::lmFanSensorsDevice.10 = STRING: IO1_SFAN_TACH
LM-SENSORS-MIB::lmFanSensorsValue.1 = Gauge32: 2439
LM-SENSORS-MIB::lmFanSensorsValue.2 = Gauge32: 2586
LM-SENSORS-MIB::lmFanSensorsValue.3 = Gauge32: 2459
LM-SENSORS-MIB::lmFanSensorsValue.4 = Gauge32: 2564
LM-SENSORS-MIB::lmFanSensorsValue.5 = Gauge32: 3409
LM-SENSORS-MIB::lmFanSensorsValue.6 = Gauge32: 0
LM-SENSORS-MIB::lmFanSensorsValue.7 = Gauge32: 3947
LM-SENSORS-MIB::lmFanSensorsValue.8 = Gauge32: 3896
LM-SENSORS-MIB::lmFanSensorsValue.9 = Gauge32: 4000
LM-SENSORS-MIB::lmFanSensorsValue.10 = Gauge32: 3896
LM-SENSORS-MIB::lmVoltSensorsIndex.1 = INTEGER: 0
LM-SENSORS-MIB::lmVoltSensorsIndex.2 = INTEGER: 1
LM-SENSORS-MIB::lmVoltSensorsIndex.3 = INTEGER: 2
LM-SENSORS-MIB::lmVoltSensorsIndex.4 = INTEGER: 3
LM-SENSORS-MIB::lmVoltSensorsIndex.5 = INTEGER: 4
LM-SENSORS-MIB::lmVoltSensorsIndex.6 = INTEGER: 5
LM-SENSORS-MIB::lmVoltSensorsIndex.7 = INTEGER: 6
LM-SENSORS-MIB::lmVoltSensorsIndex.8 = INTEGER: 7
LM-SENSORS-MIB::lmVoltSensorsIndex.9 = INTEGER: 8
LM-SENSORS-MIB::lmVoltSensorsIndex.10 = INTEGER: 9
LM-SENSORS-MIB::lmVoltSensorsIndex.11 = INTEGER: 10
LM-SENSORS-MIB::lmVoltSensorsIndex.12 = INTEGER: 11
LM-SENSORS-MIB::lmVoltSensorsDevice.1 = STRING: PS0_3_3V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.2 = STRING: PS0_5V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.3 = STRING: PS0_12V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.4 = STRING: PS0_48V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.5 = STRING: PS1_3_3V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.6 = STRING: PS1_5V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.7 = STRING: PS1_12V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.8 = STRING: PS1_48V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.9 = STRING: PS2_3_3V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.10 = STRING: PS2_5V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.11 = STRING: PS2_12V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsDevice.12 = STRING: PS2_48V_I_SENSOR
LM-SENSORS-MIB::lmVoltSensorsValue.1 = Gauge32: 6
LM-SENSORS-MIB::lmVoltSensorsValue.2 = Gauge32: 4
LM-SENSORS-MIB::lmVoltSensorsValue.3 = Gauge32: 3
LM-SENSORS-MIB::lmVoltSensorsValue.4 = Gauge32: 4
LM-SENSORS-MIB::lmVoltSensorsValue.5 = Gauge32: 6
LM-SENSORS-MIB::lmVoltSensorsValue.6 = Gauge32: 4
LM-SENSORS-MIB::lmVoltSensorsValue.7 = Gauge32: 3
LM-SENSORS-MIB::lmVoltSensorsValue.8 = Gauge32: 4
LM-SENSORS-MIB::lmVoltSensorsValue.9 = Gauge32: 6
LM-SENSORS-MIB::lmVoltSensorsValue.10 = Gauge32: 4
LM-SENSORS-MIB::lmVoltSensorsValue.11 = Gauge32: 3
LM-SENSORS-MIB::lmVoltSensorsValue.12 = Gauge32: 4

This component also reports information for switches, LEDs
and i2c's (devices accessing the i2c bus).
Because the MIB only allows us to display numeric
information a certain amount of translation has been done.

Switches:

0 = OFF
1 = ON
2 = NORMAL
3 = LOCKED
4 = UNKNOWN
5 = DIAG
6 = SECURE
99 = other

LEDs:

0 = OFF
1 = ON
2 = BLINK (this may not exist)
99 = other

i2c's:
0 = OK
99 = other

In order to prevent inordinant consumption of machine resources,
some sensor information is cached.  Currently, information
retrieved from picld is cached for six seconds.

 -- Bruce Shaw <Bruce.Shaw at shaw.ca>

------------------------------------------------------------

10.  MIB rewrites for IF-MIB, TCP-MIB and UDP-MIB

net-snmp 5.4 has started to include rewrites for the IF-MIB, TCP-MIB and
UDP-MIB implementations. They need to be explicitely enabled, though:

  ./configure --enable-mfd-rewrites ...

See the Net-SNMP Wiki (http://www.net-snmp.org/wiki/index.php/IF-MIB_rewrite)
for further details.

Thanks to Sun for the excellent patches.


 -- Thomas Anders <tanders@users.sourceforge.net>

------------------------------------------------------------

11.  Files descriptors and fopen

Solaris has a limitation on the number of file descriptors (255)
available in stdio, so that fopen() fails if more than
255 file descriptors (sockets) are open. This prevents mibs from
being loaded after 250 sockets are open, since parse.c uses stdio.

SEan <burke_sp@pacbell.net> investigated this problem, and had this
report on using the SFIO package to solve this problem.

 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The SFIO package ( http://www.research.att.com/sw/tools/sfio/ )
is a buffered streams IO package that is much more more sophisticated
than stdio, but it does support stdio API's for backward compatibility,
and that's the aspect that is important here.

To compile with SFIO, we simply add -I/usr/local/sfio/include to the
$CPPFLAGS before compiling net-snmp. This causes SFIO's stdio.h to
preempt Solaris stdio, mapping calls like fopen() and fprintf() to
the SFIO implementations. This produces a libnetsnmp that does not
have the fopen() limitation. Any application that links to this
libnetsnmp must also be linked to libsfio.

Here are the two caveats:

A. libsfio exports the functions 'getc' and 'putc', for reasons that
are not clear. These are the only symbols it exports that conflict
with stdio. While getc and putc are traditionally macros, Solaris
makes them functions in multithreaded code (compiled with -mt,
-pthread, or -D_REENTRANT). If your native stdio code links to the
libsfio versions, a crash will result.

There are two solutions to this problem. You may remove getc and putc
from libsfio, since SFIO defines getc and putc as macros, by doing:

	ar d libsfio.a getc.o
	ar d libsfio.a putc.o

or link to SFIO's stdio compatibility library, libstdio, ahead of
libsfio. This library wraps all of the native stdio calls with
versions that are safe for native or sfio streams, in case you
need to share streams between SFIO and native stdio codes.

B. libsfio provides 64-bit offsets in fseek(), ftell(). This is
a good thing, since SFIO is intended to avoid needless limitations,
but it means that SFIO's stdio.h defines off_t to be a 64-bit offset.
Net-SNMP uses readdir(), which returns a struct dirent containing
a 32-bit off_t, so the code compiled for SFIO doesn't access
struct dirent's correctly.

There are two solutions to this problem, as well. The first is to
include <dirent.h> at the start of SFIO's stdio.h. Since SFIO
defines a macro substitution for off_t, this leaves struct dirent's
definition unchanged.

An alternative, which I haven't verified, is to define _FILE_OFFSET_BITS
to be 64 when compiling libnetsnmp. According to what I see in Solaris's
/usr/include/sys/feature_tests.h, you can select a 64-bit off_t at
compile time with this setting, which should make readdir()'s off_t
compatible with SFIO's ftell(), fseek().
 [[ We have received reports that this approach does not in fact work
(see Perl discussion below)]]

Finally, thanks to Phong Vo and AT&T Labs for a fast, robust and
portable package that solves this headache very neatly.

-SEan <burke_sp@pacbell.net>

------------------------------------------------------------

12.  Perl

Net-SNMP may be compiled with Perl support by configuring like:

   ./configure -enable-embedded-perl ...

This should only be done if you are sure you really need Perl,
for the following reasons:

Solaris 8 and later ship with a version of Perl compiled using Sun's cc.

This causes a problem when attempting to compile net-snmp
with Perl functionality ie.:

   ./configure --with-mib-modules="ucd-snmp/lmSensors ucd-snmp/diskio \
      smux mibII/mta_sendmail" --enable-embedded-perl

because during the Perl section of the compile, it attempts to do so
using the methodology used to compile the original Perl, not
what you're currently using.  This can be discovered by typing:

   perl -V

and it says (among other things)

  Compiler:
    cc='cc'

and you don't have the full version of Sun's C compiler on your
system, it's going to break.

In addition if it was compiled with:

   LFS_CFLAGS      -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64

net-snmp will not compile correctly.

Given that the Perl provided with Solaris 8 (5.005_03) and Solaris 9
(5.005_03 and 5.6.1) is somewhat stale, upgrading may be to your advantage.

Perl did not ship with Solaris before version 8.  If you installed a
version from www.sunfreeware.com, it is compiled with some extra flags
that cause the net-snmp compile to break.

In either case, you will need to compile and install Perl.

There are, however, some issues.

A.  Some applications (eg. /usr/bin/kstat) require this exact version
of Perl because of libraries.  These instructions below install Perl
in /usr/local/bin (and optionally /usr/bin/).  The original is left
intact in /usr/perl5/bin/perl where, in fact, the kstat script looks
for it.  If you have version specific scripts, you will need to do
the same either by invoking /usr/perl5/bin/perl or putting:

#!/usr/perl/bin/perl -w

as the first line of your script and making it executable
(see the /usr/bin/kstat source as an example).

B.  The instructions below disable large file support.

This means that Perl would be unable to deal
successfully with files larger than 2 Gb.
Again, using /usr/perl5/bin/perl or a version compiled
with this functionality would solve this.

Hence the ideal solution is a net-snmp specific Perl in its own directory.

The following instructions will install a working Perl in /usr/local/net-snmp.

Install gcc version 3.3.2 (or later) from www.sunfreeware.com.

Download the current stable release of Perl

   http://www.cpan.org/src/stable.tar.gz

and gunzip and untar.  (This document assumes Perl 5.8.3 or later)

cd to the source directory and type the following:

  sh Configure -Dcc=gcc -Dprefix=/usr/local/net-snmp -Uinstallusrbinperl \
               -Duseshrplib -Dcf_email=your_email@your_domain \
               -Dperladmin=your_email@your_domain -Uuselargefiles -de

Replace your_email@your_domain by your real email address. If you intend
to compile Net-SNMP with Sun cc later on, replace gcc with cc above.

When it is finished, do:

   grep cppsymbols config.sh

and make sure "-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" does NOT appear.

Then do:

   make
   make test  (optional)
   make install
   /usr/local/net-snmp/bin/perl -V

if everything looks all right, compile net-snmp (see above) with the
following differences:

env PERLPROG=/usr/local/net-snmp/bin/perl ./configure --enable-embedded-perl \
 --with-mib-modules=ucd-snmp/lmSensors,ucd-snmp/diskio,smux,mibII/mta_sendmail \
 --with-cc=gcc && make && make test && make install

Make sure you specify the correct path to your self-compiled Perl binary
and use the same compiler like the one you used when building Perl above.
Feel free to add other configure options, of course.

"make test" includes some tests for the Net-SNMP Perl functionalities.

Once you have compiled and installed net-snmp you can test the Perl
capabilities of the final installation by doing the following:

Copy the perl_module.pl script found at

http://www.net-snmp.org/tutorial-5/toolkit/perl/index.html

to /usr/local/net-snmp

and modify your /usr/local/share/snmp/snmpd.conf file to contain the entry:

perl do "/usr/local/net-snmp/perl_module.pl";

then do:

/usr/local/bin/snmpwalk -v 2c -c whatever localhost .1.3.6.1.4.1.8072.999

It should return the following:

NET-SNMP-MIB::netSnmp.999.1.2.1 = STRING: "hello world"

WARNING!!  If you are planning on creating binary versions of net-snmp with
Perl capability, you will also need to ship the Perl which you created in
/usr/local/net-snmp.

 -- Bruce Shaw <Bruce.Shaw at shaw.ca>
 -- Thomas Anders <tanders@users.sourceforge.net>

------------------------------------------------------------

13.  sed

Various sed versions in older Solaris releases (Solaris 8 and earlier
at least) have serious limitations that may affect ./configure
when building net-snmp. All these issues *should* have been addressed
in net-snmp 5.4 and later. If you still have problems, please let us know
and consider:

- installing GNU sed and putting it in front of your PATH
- installing the available Sun patches for the various sed versions
  (/usr/bin/sed, /usr/xpg4/bin/sed, /usr/ucb/sed)
- try the suggestions below

The version of sed in /usr/ucb on Solaris 2.5.1 and 2.6 can't
cope with the size of the substitution strings used in config.status.

Putting /usr/bin ahead of /usr/ucb in the search path fixes this.

/usr/xpg4/bin/sed is seen to segfault under Solaris 8 when running configure.
Putting /usr/bin ahead of /usr/xpg4/bin fixes this.


 -- Thomas Anders <tanders@users.sourceforge.net>
 -- zach dot metzinger at microtune dot com

------------------------------------------------------------

14.  OpenSSL and crle

If compiling with OpenSSL (e.g. from sunsolve), it's possible that
the agent won't successfully load the crypto library (typically
in /usr/local/ssl/lib) when it is in use and will return a
cannot find library error message of some sort.

To rectify this, you will need to use the /usr/bin/crle command, which
did NOT ship with some versions of Solaris, but came as part of later
patches.  You should make sure the following patches are up to date:

107733 (Solaris 2.6)
106950 (Solaris 2.7)
109147 (Solaris 8)
115833 (Trusted Solaris 8)
112693 (Solaris 9)

Then type the following:

/usr/bin/crle

It will return something like:

Default configuration file (/var/ld/ld.config) not found
  Default Library Path (ELF):  /usr/lib (system default)
  Trusted Directories (ELF):   /usr/lib/secure (system default)

Find the location of the libcrypto libraries by typing:

find /usr -name "libcrypto*" -print

which will probably display:

/usr/local/ssl/lib/libcrypto.a
/usr/local/ssl/lib/libcrypto.so
/usr/local/ssl/lib/libcrypto.so.0
/usr/local/ssl/lib/libcrypto.so.0.9.7

which is the default installation for OpenSSL.

To include this in the loader search path, type:

/usr/bin/crle -u -l /usr/local/ssl/lib

/usr/bin/crle will now display:

Configuration file [3]: /var/ld/ld.config
  Default Library Path (ELF):   /usr/lib:/usr/local/ssl/lib
  Trusted Directories (ELF):    /usr/lib/secure  (system default)

Command line:
  crle -c /var/ld/ld.config -l /usr/lib:/usr/local/ssl/lib

If this fails, usually by displaying:

crle: /var/ld/ld.config: open failed: No such file or directory

you will need to create this directory by hand by doing the following:

mkdir /var/ld
cd /var/ld
ln -s . 32
mkdir sparcv9
chgrp bin sparcv9
ln -s sparcv9 64
touch ld.config

then do:

crle -c /var/ld/ld.config -l /usr/lib:/usr/local/ssl/lib

Thanks to Dave Shield and Johannes Schmidt-Fischer

 -- Bruce Shaw <Bruce.Shaw at shaw.ca>

------------------------------------------------------------

15. IPv6

Starting with net-snmp 5.4 you can enable the UDPIPv6 and TCPIPv6
transports on Solaris:

   ./configure --enable-ipv6

There's no support for the mibII/ipv6 mib module, though.


 -- Thomas Anders <tanders@users.sourceforge.net>

------------------------------------------------------------

16. Wish list

A.  Code cleanup

There may be opportunities for shared code between UCD-SNMP
and HOST-RESOURCES-MIB.

There may be opportunities to optimize caching perhaps
using the new auto-caching code.

B.  LM-SENSORS-MIB

We need a complete list of sensors from various platforms so
they can be displayed properly.

C.  ORACLE

How to get ORACLE's SNMP functionality to work as a sub-agent.

D. Largefile support

Rework the host mib module to work even if net-snmp is built with
largefile support. This would eliminate the most important problems
with Perl (see section 12).

 -- Bruce Shaw <Bruce.Shaw at shaw.ca>
 -- Thomas Anders <tanders@users.sourceforge.net>

------------------------------------------------------------

17.  Known Bugs!!

A.  hrDeviceTable (HOST-RESOURCES-MIB)

This section of code is only aware of disk controllers 0 through 7.
Hence, anything on controller c8 and above will be invisible.

B.  hrPartitionTable (HOST-RESOURCES-MIB)

At present, hrPartitionSize data only works for regular ufs
partitions eg. /dev/dsk/c0t0d0s0 that are mounted.  They
are displayed in partition order rather than the order
they are mounted.  Partitions mounted as mirrors, metastate
database replicas, swap or members of a RAID display size 0.

As a workaround, put entries for disks you are
interested in in snmpd.conf and examine
using UCD-SNMP-MIB.


 -- Bruce Shaw <Bruce.Shaw at shaw.ca>

------------------------------------------------------------

18.  Discussion and further information

For discussion or further information contact the coders and users
lists at http://sourceforge.net/mail/?group_id=12694 .

snmptrapd MySQL Logging
-----------------------

A trap handler for logging traps to a MySQL database was added
in release 5.5.0.

The MySQL database location and password must be configured in
/root/.my.cnf:

	[snmptrapd]
	host=localhost
	password=sql

User may also be configured, if using a MySQL user besides root.

snmptrapd.conf must be configured to for the queue size and
periodic flush interval:

	# maximum number of traps to queue before forced flush
	sqlMaxQueue 140

	# seconds between periodic queue flushes
	sqlSaveInterval 9

A value of 0 for sqlSaveInterval will completely disable MySQL
logging of traps.

The schema must be loaded into MySQL before running snmptrapd.
The schema can be found in dist/schema-snmptrapd.sql

README.systemd
--------------
Net-SNMP provides two daemons, which support systemd system manager.
See http://www.freedesktop.org/wiki/Software/systemd to learn how
systemd works. Both socket activation and notification is supported by these
daemons.

To enable systemd support, the sources must be compiled with
--with-systemd configure option.

snmpd - The SNMP agent
----------------------
Socket activation od snmpd daemon is implemented, but it's discouraged.
The reason is simple - snmpd not only listens and processes SNMP requests
from network, but also gathers system statistics counters, sends traps and
communicates with subagents. It even opens few netlink sockets.

In other words, snmpd should run from system start to properly work.
This can be done in two ways:
1) either as snmpd service unit with 'Type=notification' and without a socket
   unit
2) or as snmpd service unit with 'Type=simple', appropriate socket socket unit
   and the snmpd service enabled. This way systemd creates the snmpd listening
   socket early during boot and passes the sockets to snmpd slightly later
   (but still during machine boot). This way systemd can paralelize start of
   services, which depend on snmpd. Admins must adjust the socket file manually,
   depending if the snmpd support AgentX, IPv6, SMUX etc.

snmpd should be started with '-f' command line parameter to disable forking -
systemd does that for us automatically.


snmptrapd - The trap processing daemon
--------------------------------------
snmptrapd supports full socket activation and also notification (if needed).
Both 'Type=simple' (with appropriate socket unit) and 'Type=notify' services
will work. Again, '-f' parameter should be provided on snmptrapd command line.

If integration with SNMP agent using AgentX protocol is enabled, snmptrapd should
start during boot and not after first SNMP trap arrives. Same rules as for snmpd
applies then.

Improved Error Reporting and Thread-Safe Use of the SNMP Library

There is a need in some environments to support multiple threads
in a single application.  The SNMP Library provides the Single Session
functions which support thread-safe operation when certain precautions
are taken.  This document describes the operation of the SNMP Library
with a focus on its session management functions.  The Traditional API
and the Single API functions are compared and contrasted.
A working understanding of the CMU or UCD SNMP Library
API is recommended to fully appreciate the concepts discussed.
The document ends with a list of restrictions for using the Single API
in a multi-threaded application.

Unfortunately, the SNMPv3 support was added about the same time as
the thread support and since they occurred in parallel the SNMPv3
support was never checked for multi-threading correctness.  It is
most likely that it is not thread-safe at this time.

  ***** IMPORTANT ANNOUNCEMENT *****
  To the point, no resource locks are applied within the SNMP Library.
  The APDU encoding and some session management functions can be used
  in thread-safe manners. The MIB file parsing is not thread-safe.
  The Single Session API was made available in November 1998.
  Existing applications use the Traditional API, which is not thread-safe.
  The thread-safe considerations are discussed throughout this document.

The research and development of the Single Session API that I've completed
was wholly funded by my employer, Internet Security Systems, Inc.
and is distributed freely to the Internet community.

-Mike Slifcak, 23 April 1999

09 July 1999 Removed references to snmp_synch_setup and snmp_synch_reset


Availability

The Single Session API is integrated into the currently available
versions of the CMU SNMP library and the UC-Davis SNMP package.

 ftp://ftp.net.cmu.edu/pub/snmp/cmu-snmp-V1.13.tar.gz and later
  Read : snmp_sess_api.3, Changes.SingleSession

 ftp://ucd-snmp.ucdavis.edu/ucd-snmp-3.6.tar.gz and later
  Read : snmp_sess_api.3, README.thread (after version 3.6.1)

Both libraries work equally well in Windows NT and various
UNIX platforms.  Please read this document and refer to
the snmp_sess_api section 3 manual page.

Glossary of Terms

APDU    Application Protocol Data Unit
API     Application Programming Interface
CMU     Carnegie-Mellon University, Pittsburgh, PA.
Library The SNMP library; Both CMU and UCD versions are applicable.
Session Concept embodying the management of transacting SNMP APDUS.
SNMP    Simple Network Management Protocol
UCD     University of California at Davis, CA.

Introduction

The Library extends the UNIX file concept (open, close, read, write) to a Session.
Opening a Session binds a local socket to a well-known port and creates internal
structures to help with controlling the transaction of SNMP APDUs.  Closing a
Session releases the memory and system resources used for these purposes.

Since the mid-1980s, many SNMP applications have used the Traditional Session
API to transact SNMP APDUs between the local host and SNMP-enabled devices.

  The Traditional Session API does not support multi-threaded applications:

  1)  There are no resource locks to prevent exposing the Library's
      global data resources to corruption in a multi-threaded application;

  2)  The Traditional API functions that receive SNMP APDUs
      do not provide an interface for one of many sessions;

  3)  Errors discovered by the Library are communicated through global
      data structures and are not associated with the session
      in which the error occurred.

  The Single Session API provides these capabilities:

  1)  Manage a single SNMP session safely, in multi-threaded or
      non-threaded applications, by avoiding access to data structures
      that the Traditional Session API may share between Sessions;

  2)  Associate errors with the session context for threaded
      and non-threaded applications.


Contrasting and Comparing Traditional API and Single API

The Traditional API uses the struct snmp_session pointer returned
from snmp_open() to identify one SNMP session.  The Single API uses
the opaque pointer returned from snmp_sess_open() to identify one
SNMP session.

   Helpful Hint : The Library copies the contents of the
   structure which is input to snmp_open() and snmp_sess_open().
   Once copied, changing that input structure's data
   has no effect on the opened SNMP Session.

The Traditional API uses the snmp_error() function to identify any
library and system errors that occurred during the processing for
one SNMP session.   The Single API uses snmp_sess_error() for the
same purpose.

The Traditional API manages the private Sessions list structure;
adding to the list during snmp_open(), removing during snmp_close.

With few exceptions, the Traditional API calls the Single API
for each session that appears on the Sessions list.

The Traditional API reads from all Sessions on the Sessions list;
The Single API does not use the Sessions list.
The Single API can read from only one Session.

   Helpful Hint :
   This is the basis for thread-safe-ness of the Library.
   There are no resource locks applied.


Using the Single API

A multi-threaded application that deploys the SNMP Library should
should complete all MIB file parsing before additional threads
are activated.  Drawing from the parsed contents of the MIB does
not incur any data corruption exposure once the internal MIB structures
are initialised.

The application may create threads such that a single thread may manage
a single SNMP session.  The thread should call snmp_sess_init()
to prepare a struct snmp_session structure.  The thread can adjust
session parameters such as the remote UDP port or the local UDP port,
which must be set prior to invoking snmp_sess_open().

The first call to snmp_sess_init() initialises the SNMP Library,
including the MIB parse trees, before any SNMP sessions are created.
Applications that call snmp_sess_init() do not need to read MIBs
nor setup environment variables to utilize the Library.

After the struct snmp_session is setup, the thread must call
snmp_sess_open() to create an SNMP session.  If at any time
the thread must change the Session configuration,
snmp_sess_session() returns the pointer to the internal configuration
structure (a struct snmp_session, copied from snmp_sess_open).
The thread can adjust parameters such as the session timeout
or the community string with this returned struct snmp_session pointer.
Changes to the remote or local port values have no effect on an opened Session.

The thread can build PDUs and bind variables to PDUs, as it performs its duties.
The thread then calls snmp_sess_send() or snmp_sess_async_send() to build and send
an SNMP APDU to the remote device. If a Get-Response-PDU is expected, the thread
should call snmp_sess_synch_response() instead.

When the thread is finished using the session, it must free the resources
that the Library used to manage the session.
Finally, the thread must call snmp_sess_close() to end the Session.

Snmp_sess_init(), snmp_open(), and snmp_sess_open()
must use the same calling parameter for a given Session.
Other methods should use only the returned parameter from
snmp_open() and snmp_sess_open() to access the opened SNMP Session.


Error Processing

Two calls were added : snmp_error() and snmp_sess_error() return the
"errno" and "snmp_errno" values from the per session data, and a string
that describes the errors that they represent.  The string must be freed
by the caller.

Use snmp_error() to process failures after Traditional API calls,
or snmp_sess_error() to process failure after Single API calls.
In the case where an SNMP session could not be opened,
call snmp_error() using the struct snmp_session supplied to either snmp_open()
or snmp_sess_open().


The following variables and functions are obsolete and may create problems
in a multi-threaded application :

  int    snmp_errno
  char * snmp_detail
  snmp_set_detail()
  snmp_api_errstring()


Function Summary

The functions in the following table are functionally equivalent,
with the exception of these behaviors:
- The Traditional API manages many sessions
- The Traditional API passes a struct snmp_session pointer,
       and touches the Sessions list
- The Single API manages only one session
- The Single API passes an opaque pointer, and does not use Sessions list

  Traditional        Single                    Comment
  ===========        ==============            =======
  snmp_sess_init     snmp_sess_init            Call before either open
  snmp_open          snmp_sess_open            Single not on Sessions list
                     snmp_sess_session         Exposes snmp_session pointer
  snmp_send          snmp_sess_send            Send one APDU
  snmp_async_send    snmp_sess_async_send      Send one APDU with callback
  snmp_select_info   snmp_sess_select_info     Which session(s) have input
  snmp_read          snmp_sess_read            Read APDUs
  snmp_timeout       snmp_sess_timeout         Check for timeout
  snmp_close         snmp_sess_close           Single not on Sessions list
 snmp_synch_response snmp_sess_synch_response  Send/receive one APDU
  snmp_error         snmp_sess_error           Get library,system errno


Example 1 : Traditional API use.

    #include "snmp_api.h"
      ...
      int liberr, syserr;
      char *errstr;
      struct snmp_session Session, *sptr;
      ...
      snmp_sess_init(&Session);
      Session.peername = "foo.bar.net";
      sptr = snmp_open(&Session);
      if (sptr == NULL) {
          /* Error codes found in open calling argument */
          snmp_error(&Session, &liberr, &syserr, &errstr);
          printf("SNMP create error %s.\n", errstr);
          free(errstr);
          return 0;
      }
      /* Pass sptr to snmp_error from here forward */
      ...
      /* Change the community name */
      free(sptr->community);
      sptr->community = strdup("public");
      sptr->community_len = strlen("public");
      ...
      if (0 == snmp_send(sptr, pdu)) {
          snmp_error(sptr, &liberr, &syserr, &errstr);
          printf("SNMP write error %s.\n", errstr);
          free(errstr);
          return 0;
      }
      snmp_close(sptr);


Example 2 : Single API use.

    #include "snmp_api.h"
      ...
      int liberr, syserr;
      char *errstr;
      void *sessp;  /* <-- an opaque pointer, not a struct pointer */
      struct snmp_session Session, *sptr;
      ...
      snmp_sess_init(&Session);
      Session.peername = "foo.bar.net";
      sessp = snmp_sess_open(&Session);
      if (sessp == NULL) {
          /* Error codes found in open calling argument */
          snmp_error(&Session, &liberr, &syserr, &errstr);
          printf("SNMP create error %s.\n", errstr);
          free(errstr);
          return 0;
      }
      sptr = snmp_sess_session(sessp); /* <-- get the snmp_session pointer */

      /* Pass sptr to snmp_sess_error from here forward */
      ...
      /* Change the community name */
      free(sptr->community);
      sptr->community = strdup("public");
      sptr->community_len = strlen("public");
      ...
      if (0 == snmp_sess_send(sessp, pdu)) {
          snmp_sess_error(sessp, &liberr, &syserr, &errstr);
          printf("SNMP write error %s.\n", errstr);
          free(errstr);
          return 0;
      }
      snmp_sess_close(sessp);

Example 3. Differences Between Traditional API and Single API Usage
5a6
>       void *sessp;  /* <-- an opaque pointer, not a struct pointer */
11,13c12,14
<       sptr = snmp_open(&Session);
<       if (sptr == NULL) {
---
>       sessp = snmp_sess_open(&Session);
>       if (sessp == NULL) {
19c20,22
<       /* Pass sptr to snmp_error from here forward */
---
>       sptr = snmp_sess_session(sessp); /* <-- get the snmp_session pointer */
>
>       /* Pass sptr to snmp_sess_error from here forward */
26,27c29,30
<       if (0 == snmp_send(sptr, pdu)) {
<           snmp_error(sptr, &liberr, &syserr, &errstr);
---
>       if (0 == snmp_sess_send(sessp, pdu)) {
>           snmp_sess_error(sessp, &liberr, &syserr, &errstr);
33c36
<       snmp_close(sptr);
---
>       snmp_sess_close(sessp);


Restrictions on Multi-threaded Use of the SNMP Library

  1. Invoke SOCK_STARTUP or SOCK_CLEANUP from the main thread only.

  2. The MIB parsing functions use global shared data and are not
     multi-thread safe when the MIB tree is under construction.
     Once the tree is built, the data can be safely referenced from
     any thread.  There is no provision for freeing the MIB tree.
     Suggestion: Read the MIB files before an SNMP session is created.
     This can be accomplished by invoking snmp_sess_init from the main
     thread and discarding the buffer which is initialised.

  3. Invoke the SNMPv2p initialisation before an SNMP session is created,
     for reasons similar to reading the MIB file.
     The SNMPv2p structures should be available to all SNMP sessions.
     CAUTION: These structures have not been tested in a multi-threaded
     application.

  4. Sessions created using the Single API do not interact with other
     SNMP sessions.  If you choose to use Traditional API calls, call
     them from a single thread.  The Library cannot reference an SNMP
     session using both Traditional and Single API calls.

  5. Using the callback mechanism for asynchronous response PDUs
     requires additional caution in a multi-threaded application.
     This means a callback function probably should probably not use
     Single API calls to further process the session.

  6. Each call to snmp_sess_open() creates an IDS.  Only a call to
     snmp_sess_close() releases the resources used by the IDS.

Some notes for the Tru64 Unix 5.x port
======================================

1. Compiling
------------

The following procedure has been proven to successfully compile net-snmp
version 5.2.2 and later on Tru64 Unix 5.1B (Alpha EV5.6) using the Compaq C 6.5
compiler:

	./configure --disable-embedded-perl
	make
	su -
	make install

A recent GNU C compiler (gcc) will probably work, too.

Please note that the "host" module doesn't compile on Tru64, so you *cannot*
run configure with "--with-mib-modules=host".

2. Embedded Perl
----------------

The Perl package (5.00503) shipped with Tru64 Unix 5.1 isn't complete enough
to allow to build net-snmp with embedded Perl support. If you need embedded
Perl support, do your own Perl installation first.

3. IPv6
-------

Starting with net-snmp 5.4 you can enable the UDPIPv6 and TCPIPv6 transports
on Tru64 Unix 5.1:

   ./configure --enable-ipv6

There's no support for the IPv6 MIBs, though.


4. Known problems
-----------------

"make test" is known to report the following failure:

  59: testing full snmpwalk (SNMPv2c) against agent (may take time)... FAIL

so it's obvious that there are still problems with some MIB modules on Tru64.
If you have ideas how to fix them, please let us know!


5. Feedback
-----------

Please also see README and PORTING.

If you have questions, additional insights or (even better) patches regarding
net-snmp on Tru64 Unix, please refer to the net-snmp mailing lists (see
http://www.net-snmp.org/lists).

***************************************************************************
*
* README.win32
*
***************************************************************************

This guide describes how to build Net-SNMP with Microsoft Visual Studio,
Cygwin, MinGW or Mingw-w64.  As developers build with other Win32
environments, their notes will be included here.

The sections in this guide are:

Current Status for Win32 platforms
Interactions with Other Vendor's Products
Running Net-SNMP as a replacement for the Microsoft SNMP service
Co-existence with Microsoft SNMP services
Microsoft Visual C++ - Overview
Microsoft Visual C++ - Configure / nmake - Building
Microsoft Visual C++ - Workspace - Building
Microsoft Visual C++ - Workspace - Building the DLL
Microsoft Visual C++ - Workspace - Building the Perl SNMP modules
Microsoft Visual C++ - Workspace - Installing
Microsoft Visual C++ - Building with OpenSSL
Microsoft Visual C++ - Building with IPv6
Microsoft Visual C++ - Building your own applications with snmplib
Microsoft Visual C++ - Extending the Agent
GCC on Windows
Cygwin - Building
MinGW - Building
MinGW - Building with OpenSSL
Configuring Net-SNMP
How to Register the Net-SNMP Agent and Trap Daemon as Windows services
Notes on SET support for WIN32 ports
Notes on preprocessor defines for Microsoft Visual Studio, MinGW and Cygwin
Acknowledgements


***************************************************************************
*
* Net-SNMP status for Win32 platforms
*
***************************************************************************

All applications build with Microsoft Studio, Cygwin, MinGW and Mingw-w64.

  -  All of the applications work (snmpwalk, snmpget, snmpset, snmptrap, ...).
  -  The system, snmp, ip, tcp, udp and icmp MIB-groups work.
  -  The Net-SNMP agent runs as an AgentX master agent or as subagent.
  -  smux is working.
  -  The target, notification, disman/mte groups compile but are not tested.
  -  The TCP/IPv6 and UDP/IPv6 transports compile but are not tested.
  -  Extending the agent to support enterprise-specific MIBs works.
  -  Running the agent on a non-standard UDP or TCP port works.
  -  Snmpd can be registered as a Windows service.
  -  Snmptrapd can be registered as a Windows service.
  -  Some build environments allow long pathnames that contain
     embedded spaces.  As this is not true for Cygwin "configure",
     the documented example scripts will refer to "c:/usr"
     as the base directory for installed Net-SNMP software.
  -  When using the winExtDLL extension agent, the Net-SNMP agent will
     load the Windows SNMP Service extension DLLs.

The next subsection relates to items that are built using Visual Studio

  -  All Debug and Release targets linked with libsnmp project targets
     build without errors, and are fully functional.

  -  With Visual Studio 2005 and later, the Net-SNMP source code can be
     compiled into either 32-bit or 64-bit executables (the amd64/x64
     architecture). Previous Visual Studio versions support 32-bit executables
     only.


***************************************************************************
*
* Interactions with Other Vendor's Products
*
***************************************************************************

  -  Install scripts etc are written assuming Windows NT / 2000 or higher

  -  Running the Net-SNMP Agent or trap receiver on Windows 95 or Win3.1
     is not supported.

  -  Running the Net-SNMP Agent or trap receiver as a service on Windows 95
     or Windows 98 is not supported.

  -  The Net-SNMP agent and trap receiver will fail to start if either
     cannot bind to their connect port (161 for agent, 162 for trap receiver).
     Check the Services panel to be sure no other SNMP program conflicts. See
     the section titled 'Co-existence with Microsoft SNMP services' below.

  -  The Net-SNMP agent can be used instead of the MS supplied one while
     retaining all functionality and with slightly better SNMP conformance.
     See the section titled 'Co-existence with Microsoft SNMP services' below.

  -  The Net-SNMP agent does not use the MS SNMP.dll, therefore it cannot
     run as an extensible part of the MS agent.  It is possible to use a third
     party proxy agent for the MS agent to 'proxy' requests to the Net-SNMP
     agent listening on a different UDP port on the same machine.

  -  Snmptrapd does not "share" nor multiplex traps with SNMPTRAP.EXE,
     a program that is available from Microsoft or ACE#COMM.


***************************************************************************
*
* Running Net-SNMP as a replacement for the Microsoft SNMP service
*
***************************************************************************

As of Net-SNMP 5.4, the Net-SNMP agent is able to load the Windows SNMP
service extension DLLs by using the Net-SNMP winExtDLL extension.

The Windows SNMP service must be installed, but the service must be disabled.
This is required so that the extension DLLs are available for loading, and
also because this extension and the existing Windows extensions use the
Windows SNMP API from snmpapi.dll.

An alternative to winExtDLL is to proxy requests from Net-SNMP to the Windows
SNMP service.  See the section 'Co-existence with Microsoft SNMP services'.


Limitations
-----------

- When using HP Insight Agents, some parts of the enterprises.232 tree are not
  accessible.  The cause of this is not known.

- When using winExtDLL, there is an offset of up to one second between the
  value of the sysUpTime varbind included in the traps generated by SNMP
  extension DLLs (e.g. linkUp and linkDown) and the value of the sysUpTime
  varbind included in traps generated by Net-SNMP itself (e.g. coldStart).

- When using winExtDLL, hrSystemUptime.0 reports the system uptime in thousands
  of a second instead of hundreds of a second. This is well known behavior of
  the Microsoft DLL that implements this MIB object. For more information,
  see also https://connect.microsoft.com/onecare/feedback/ViewFeedback.aspx?FeedbackID=504908.


Enabling the Windows SNMP extension agents
------------------------------------------

When installing Net-SNMP using the binary available from the web site, select
'With Windows Extension DLL support' for the 'Net-SNMP Agent Service'.

The recommended way to start snmpd is with the following command line:

 snmpd.exe -I-udp,udpTable,tcp,tcpTable,icmp,ip,interfaces,system_mib,sysORTable

The above command will exclude all the Net-SNMP extensions that overlap with
the default Windows (2003) extensions included with Windows.  Other Net-SNMP
modules take precedence over the modules loaded by winExtDLL.

The binary install of Net-SNMP includes shortcuts in the Start menu for
registering and unregistering snmpd and snmptrapd as a service with the
correct command line options.

A simple test to see if winExtDLL is working is to get the sysDescr string.

 snmpget -v 1 -c public localhost sysDescr.0

If you see something similar to:

 Hardware: x86 Family 15 Model 12 Stepping 0 AT/AT COMPATIBLE - Software:
 Windows 2000 Version 5.0 (Build 2195 Uniprocessor Free)

instead of the usual Net-SNMP:

 Windows host1 5.0.2195 Service Pack 4 2000 Server x86 Family 15 Model 12
 Stepping 0

then it's using the Windows DLLs.  You may also notice that your floppy
drive is accessed when starting the service.  This is from one of the
Windows extensions.

To see what Windows modules are being loaded, you can shut down the
service and then run snmpd.exe from the command line with winExtDLL
debugging enabled using (all on one line):

 snmpd.exe -Lo -I-udp,udpTable,tcp,tcpTable,icmp,ip,interfaces,system_mib,
 sysORTable -DwinExtDLL

The Windows DLL snmpmib.dll (SNMPMIB) contains SNMP traffic statistics
(.1.3.6.1.2.1.11).  As we are using Net-SNMP and not the Windows SNMP Service,
no values will be returned from the Windows extension.  To allow SNMP
statistics to be received, the Net-SNMP module snmp_mib is permitted to load
by not excluding it in the above command line.  As stated above, this module
will take precedence over the Windows module.


Registry Information
--------------------

Warning:  Improper use of the registry editor can damage to your operating
          system and should only be used by experienced users.

The following registry keys are used by the Windows SNMP Service to determine
what extension DLLs to load:

HKLM\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents

Each REG_SZ value contains the registry path to an extension agent which
contains the path to the DLL.  For example:

Name    Type    Value
1       REG_SZ  SOFTWARE\Microsoft\LANManagerMIB2Agent\CurrentVersion

To prevent winExtDLL from loading the above extension, change the registry
path to an invalid path such as:

Name    Type    Value
1       REG_SZ  SOFTWARE\Microsoft\LANManagerMIB2Agent\CurrentVersion!!!


Service dependencies
--------------------

Services that depend on the SNMP Service will have to be modified to depend on
Net-SNMP instead of SNMP by modifying the registry.  See Microsoft article
193888 for more information.


Compiling Net-SNMP with the winExtDLL extension
-----------------------------------------------

To build Net-SNMP with the winExtDLL extension, add --with-winextdll to the
configure command line.


***************************************************************************
*
* Co-existence with Microsoft SNMP services
*
***************************************************************************

If the Microsoft SNMP agent service (SNMP Service) is running, the Net-SNMP
agent (snmpd) will fail to start as it will not be able to bind to the default
TCP/IP port of 161.

If the Microsoft SNMP Trap Receiver service is running, the Net-SNMP trap
receiver (snmptrapd) will fail to start as it will not be able to bind to the
default TCP/IP port of 162.

It is not a requirement to install the Net-SNMP agent (snmpd) or trap receiver
(snmptrapd).  All the command line utilities such as snmpget.exe, snmpset.exe
and the Perl modules will work without the Net-SNMP services.  All the
utilities will work against any SNMP agent.

The main benefit of running the Microsoft SNMP agent instead of the Net-SNMP
agent is that many Windows applications such as Microsoft SQL Server,
Microsoft Exchange etc, extend the Microsoft agent.  Net-SNMP is NOT a drop
in replacement for the Microsoft agent unless the winExtDLL Net-SNMP extension
is used (see the section 'Running Net-SNMP as a replacement for the Microsoft
SNMP service').  Running Net-SNMP in place of the Microsoft agent (without
winExtDLL) will prevent the other applications from working with SNMP.  Also,
the Net-SNMP agent does not contain as many MIBs as the Microsoft agent.  For
example, as of August 2005, the HOST-RESOURCES (host) MIB is not yet
implemented in Net-SNMP.

There are many benefits of running the Net-SNMP agent instead of the Microsoft
such as you can extend the agent using various features found in snmpd.conf
such as pass and pass_persist (support for others are being added), you can
use SNMP v3, and there is more granular access control.

To allow both the Microsoft and Net-SNMP agent / trap receiver to run at the
same time, the default TCP/IP port must be changed on either the Microsoft or
Net-SNMP version of the application.

The Net-SNMP ports for snmpd and snmptrapd can be modified via snmpd.conf and
snmptrapd.conf or by using a command line option with each program.  See the
Net-SNMP Help file for instructions on changing the port number.

The Microsoft services use the 'snmp' and 'snmptrap' entries in the SERVICES
file (%SystemRoot%\system32\drivers\etc\services) to determine the port to bind
the service to when the service starts.  Simply modify the entries and restart
the affected services.

Note:  Changing the default port the service listens on will prevent it from
       accepting requests or receiving traps from standard SNMP devices and
       management stations unless they have also been reconfigured to use the
       new port numbers.

It is possible to configure Net-SNMP agent to listen on the default UDP port
(161), have the Microsoft agent listen on another port such as 1161, and have
Net-SNMP proxy (forward) requests to the Microsoft agent.  This will allow you
to use the advanced features of Net-SNMP while still being able to query
the Microsoft agent and subagents.  To this, follow these steps:

 1.  Change the port that the Microsoft agent listens on.

 2.  Configure the Microsoft agent to only accept requests from localhost.
     This can be set in the Security tab for the SNMP service in Windows 2000+.
     This is recommended to prevent users from querying the Microsoft agent
     directly.

 3.  Add a r/c community string to the Microsoft agent.  This can be set in
     the Security tab for the SNMP service in Windows 2000+.  This will give
     Net-SNMP full SNMP access.  User access can be restricted by Net-SNMP
     as explained below.

 4.  Restart the Microsoft SNMP service.

 5.  Configure Net-SNMP to proxy requests to the Microsoft agent.  To have it
     forward ALL requests to the Microsoft agent, add the following line to
     snmpd.conf:

       proxy  -v 1 -c public localhost:1161 .1.3

     To only forward a section of the MIB tree such as the host section, use:

       proxy  -v 1 -c public localhost:1161 host

 6.  Start the Net-SNMP agent.

     Notes: If Net-SNMP has built in support for an OID and the proxy statement
            is not for a specific OID, then it will respond instead of proxying
            the request.  For example, if you proxy the 'system' tree and issue
            an snmpget for sysDescr.0, Net-SNMP will respond with it's own
            version of sysDescr.0 instead of forwarding it.  To prevent Net-SNMP
            from doing this, you must prevent the system MIB from being
            initialized when snmpd.exe is started by specifying what MIBS to
            initialize using the -I switch.

            If you are forwarding everything to the Microsoft agent (.1.3),
            start snmpd.exe using:

              snmpd.exe -Ivacm_conf,proxy,pass,pass_persist

            The above will enable proxy, pass and pass_persist support.  See the
            snmpd man page for more information on the -I switch.

            If you are forwarding a section of the tree that is not implemented
            in Net-SNMP such as 'host', you do not need to use the -I switch as
            Net-SNMP will forward the request.  This may cause issues in the
            future if newer versions of Net-SNMP implement the section of the
            tree you are forwarding, such as the HOST-RESOURCES MIB.

            The pass and pass_persist commands will work even if the entire
            tree is proxied to the Microsoft Agent.

 7.  Test the agent.  If you have forwarded the entire tree, issue an snmpget
     for sysDescr.0.  For example:

       snmpget -v 1 -c public localhost sysDescr.0

     The Microsoft agent will respond in a format similar to:

       Hardware: x86 Family 15 Model 12 Stepping 0 AT/AT COMPATIBLE - Software:
        Windows 2000 Version 5.0 (Build 2195 Uniprocessor Free)

     The Net-SNMP agent would normally respond in a format similar to:

       Windows host1 5.0.2195 Service Pack 4 2000 Server x86 Family 15 Model 12
        Stepping 0

If you had previously configured the Microsoft agent with multiple community
strings to restrict who can read and write to the OID tree, the security
settings should be transferred to snmpd.conf.  For example, if the Microsoft
agent was configured with:

 Community              Rights
 ---------------------------------
 public                 read
 S3cur39876             read/write
 Sn0wb0ard345           read/create

Add the following to snmpd.conf:

 rocommunity  public
 rwcommunity  S3cur39876
 rwcommunity  Sn0wb0ard345

It is possible to add more granular security using Net-SNMP.  For example, to
restrict the public community string to only read the system tree, use:

 rocommunity  public 0.0.0.0 system

See the snmpd.conf man page for more information on configuring security.


***************************************************************************
*
* Microsoft Visual Studio - Overview
*
***************************************************************************

nmake is required to build Net-SNMP with Microsoft Visual Studio.

To use nmake on the command line, the Configure script is run first to create
the various makefiles.  Once these have been created, nmake is used to build
the applications.  Perl is required to use this method, as the Configure
script is written in Perl.  Perl source code is available at:

        https://www.cpan.org/src/

The make file system is based on and uses the directory structure of the
projects contained in the Workspace files which are described below.  It is
recommended that you read and understand how the workspaces are configured
even if you will only be using the command line Configure / nmake system.

If you want to distribute the generated executable, you will also need
to distribute the Microsoft Visual Studio Redistributable Package. Check the
EULA included with that package before redistributing it.

OpenSSL is required to support the encryption capabilities in SNMPv3,
or SHA authentication.

Since the Microsoft Visual Studio build environment does not natively use
"configure" nor "make" to generate the various pathnames that the programs
require, the header files need to be manually modified when using the IDE, and
an install script is provided.  When using the Perl Configure / nmake system,
the header files are automatically modified and require no manual editing.

The projects are arranged so that ALL of the usable products, the .exe files,
are written to the win32\bin directory.  The win32\lib directory is used only
to build the the files in the win32\bin directory.  Once building is
completed, there is no further use for the files in the win32\lib directory.

***************************************************************************
*
* Microsoft Visual Studio - Configure / nmake - Building
*
***************************************************************************

There are two ways to build Net-SNMP using the Configure / nmake system.
The first and easiest method is by running the win32\build.bat script.  The
second is manually running Configure and nmake.

Note:  Perl is required to use this method as the Configure script is
       written in Perl.  The Perl source code is available at:

        https://www.cpan.org/src/

The Perl interpreter can be built as follows:
1. Extract the Perl source code archive.
2. In win32/Makefile, change CCTYPE to the string that corresponds to your
   Visual Studio version, e.g. MSVC140.
3. Edit INST_DRV and INST_TOP if necessary.
4. Run vcvarsall.bat.
5. Run nmake.
6. Run nmake install.

Win32\build.bat script
======================

The build.bat script is an easy menu driven system that allows you to select
how Net-SNMP should be built, and where it should be installed.  Follow these
steps to build using build.bat:

1.  Open a command prompt

2.  When building with OpenSSL, set the environment variables INCLUDE and LIB
    such that these point at the proper OpenSSL directories. An example:

    set INCLUDE=C:\OpenSSL-Win32\include
    set LIB=C:\OpenSSL-Win32\lib\VC\static

3.  Initialize the Visual Studio build environment by running vcvarsall.bat
    which can be found in the bin folder of your Visual Studio install folder.
    If you want to generate 64-bit binaries instead of 32-bit binaries, run
    vcvarsall.bat with the amd64 argument. See also "How to: Enable a 64-Bit
    Visual C++ Toolset at the Command Line" for more information
    (http://msdn.microsoft.com/en-us/library/x4d2c09s%28v=vs.80%29.aspx).

4.  Run win32\build.bat

5.  The following screen will appear:

    Net-SNMP build and install options
    ==================================

    1.  OpenSSL support:                disabled
    2.  OpenSSL include directory:      C:\OpenSSL-Win64\include
    3.  OpenSSL library directory:      C:\OpenSSL-Win64\lib\VC
    4.  Platform SDK support:           disabled

    5.  Install path:                   c:/usr
    6.  Install after build:            enabled

    7.  Perl modules:                   disabled
    8.  Install perl modules:           disabled

    9.  Quiet build (logged):           enabled
    10. Debug mode:                     disabled

    11. IPv6 transports (requires SDK): disabled
    12. winExtDLL agent (requires SDK): disabled

    13. Link type:                      static

    14. Install development files       disabled

    F.  Finished - start build
    Q.  Quit - abort build

    Select option to set / toggle:

6.  Toggle the options on and off as desired by typing the line number
    followed by <enter>.

    To compile with OpenSSL, the OpenSSL library and header files must
    already be installed.  See the section 'Microsoft Visual C++ - Building
    with OpenSSL' for details.

    To use the IPv6 transports, Windows 98 or later is required.

    See the section 'Running Net-SNMP as a replacement for the Microsoft
    SNMP service' for important information on using the winExtDLL agent.

    If Quiet mode is enabled, all build activity is stored in various *.out
    files inside of the win32 folder.

    When you are ready to build, type f <enter>

7.  Building will begin.  Following is a sample screen shot of a quiet build:

    Building...

    Deleting old log files...
    Running Configure...
    Cleaning...
    Building main package...
    Installing main package...
    Running Configure for DLL...
    Cleaning libraries...
    Building DLL libraries...
    Installing DLL libraries...
    Cleaning Perl....
    Building Perl modules...
    Testing Perl modules...
    Installing Perl modules...

    See perlmake.out for Perl test results

    Done!

8.  If the folder that Net-SNMP was installed to is ever changed, modify the
    system environment variables or registry keys as explained in the
    'Configuration_Overview.html' file located in win32/dist/htmlhelp.


Manual build using Configure / nmake
====================================

To build using nmake on the command line, the make files need to be generated
first by the Configure script.  Following are sample steps to:

  -enable Platform SDK support
  -enable OpenSSL support
  -enable debug mode
  -build Net-SNMP
  -install to 'c:\usr'
  -compile the Perl modules
  -test the Perl modules
  -install the Perl modules

1.  Open a command prompt

2.  Initialize the Visual Studio build environment by running VCVARS32.bat
    which can be found in the bin folder of your Visual Studio install folder.

3.  Run the following command:

      perl Configure --with-sdk --with-ssl --config=debug --prefix="c:/usr"

4.  The make files will be generated, and a configuration summary will appear:

    ---------------------------------------------------------
                Net-SNMP configuration summary:
    ---------------------------------------------------------

      Config type:                debug
      SDK:                        enabled
      Link type:                  static
      Prefix / Destdir:           c:/usr
      OpenSSL:                    enabled

5.  Type:

      nmake clean
      nmake
      nmake install

      perl Configure --with-sdk --with-ssl --config=debug --linktype=dynamic\
           --prefix="c:/usr"

      nmake libs_clean
      nmake libs
      nmake install

      nmake perl_clean
      nmake perl
      nmake perl_test
      nmake perl_install

For a complete list of Configure options, run:

  perl Configure --help

For a complete list of possible build targets, after generating the make files
using Configure, run:

  nmake help

Note:  The Configure option --linktype=static (or not specifying a linktype)
       will result in libsnmp being compiled and all other components being
       statically linked to it.

       The Configure option --linktype=dynamic will result in libsnmp_dll
       (netsnmp.dll) being compiled and all other components being dynamically
       linked to it.


***************************************************************************
*
* Microsoft Visual Studio - Building with OpenSSL
*
***************************************************************************

OpenSSL is required to support the encryption capabilities in SNMPv3
(or SHA authentication). Pre-compiled binaries are available from
http://www.slproweb.com/products/Win32OpenSSL.html.


***************************************************************************
*
* Microsoft Visual Studio - Building your own applications with snmplib
*
***************************************************************************

Linking in an snmplib built to use the Multithreaded DLL runtime library to
an application configured for the Debug Multithreaded DLL runtime library
results in a link error along the lines of 'defaultlib "MSVCRT" conflicts
with use of other libs'.   If you receive a similar message, check that the
projects settings between library and application match up.

To successfully build your existing project with Net-SNMP libraries,
change the project settings FOR YOUR APPLICATION ONLY as follows:

   1. In the Link section, Select "Additional Libraries".
      Add netsnmp.lib for Release version.
      Add netsnmp_d.lib for Debug version.

   2. Remove all references to these libraries:
      libsnmp*.lib msvcrt*.lib libc*.lib oldnames.lib

   3. In the C++ section, Select "Code Generation".
      For Release, select /MD or "MultiThreaded DLL".
      For Debug, select /MDd or "Debug MultiThreaded DLL".

   4. Make sure "Ignore all default libraries" is NOT SET.

   5. Make sure "_MBCS" is included in your pre-processor defines.

Note: Some users may have better results compiling other packages that use
      the installed header files by removing the "mode_t" definition from
      net-snmp-config.h file in the installed directories.


***************************************************************************
*
* Microsoft Visual Studio - Extending the Agent
*
***************************************************************************

Assuming that the MIB compiler generated the my.h and my.c files for the
custom MIB "my", the following changes are required to extend the agent
using VC++:

   - Add the my.h and my.c files to your 'netsnmpmibs' project in VC++.
   - Next edit the '<sourcedir>\win32\mib_module_includes.h' file to
     add an include to your .h file.

        #include "mibgroup/my.h"

   - Next edit the '<sourcedir>\win32\mib_module_inits.h' file to add
     code to call your initialize function.

        if (should_init("my")) init_my();

That's all that is needed. Now go ahead and compile the 'netsnmpmibs'
and 'snmpd' project. And things should work just fine.


***************************************************************************
*
* GCC on Windows
*
***************************************************************************

There are multiple versions of GCC (the GNU Compiler Collection) in common use
on Microsoft Windows operating systems. This section will attempt to point the
user to the information required to choose the one to best suit their needs.

Cygwin

The Cygwin compiler and toolkit provides a Unix style shell and environment
for Windows based systems. The cygwin1.dll provides a POSIX emulation layer
that simplifies porting Unix / Linux applications to Windows. The Cygwin dlls
are required if an application is to be distributed. The dependency on the
The Cygwin tool chain and documentation can be found at:

http://sources.redhat.com/cygwin/


MinGW and Mingw-w64

The MinGW projects provide a Windows native version of gcc. The tool chain
links against existing Windows dlls found on most systems. Binaries compiled
with MinGW do not require additional libraries to be distributed. The MSYS
and MSYS2 environments provide a shell (Bash) and tools to emulate a Unix style
build environment on Windows. Mingw-w64 is an improved version of MinGW which
supports both 32-bit and 64-bit environments.

MSYS + MinGW
============

The MinGW and MSYS tools and documentation can be found at:

http://www.mingw.org


***************************************************************************
*
* Cygwin - Building
*
***************************************************************************

An alternate way to build and run Net-SNMP on Win32 is to use the Cygwin
environment.  Detailed information about the Cygwin environment is available
on the web at: http://sources.redhat.com/cygwin/.

Cygwin allows you to compile almost the complete agent and applications.
As an example, the following configure options create a working set of
programs:

ENV_SEPARATOR=":" \
./configure \
	--with-mib-modules="host agentx disman/event-mib examples/example" \
	--with-out-mib-modules=host/hr_network \

If you want to disable SNMPv3 auth and privacy features, add:
	--without-openssl \

If you want to use IPv6 transports, add:
	--enable-ipv6

Note: the source code should *not* be in a folder that contains a space.
For example, compiling in your 'My Documents' folder or your Desktop folder
(usually c:\Documents and Settings\xxxx\Desktop) is not supported.

If the folder that Net-SNMP was installed to is ever changed, modify the
system environment variables or registry keys as explained in the
'Configuration_Overview.html' file located in win32/dist/htmlhelp.


***************************************************************************
*
* MinGW - Building
*
***************************************************************************

MinGW, MSyS and the associated documentation can be downloaded from
http://www.mingw.org.

Compiling net-snmp with MinGW requires GNU regex and libintl. Binaries and
developer header files for these libraries can be installed by running the
following command from a MinGW shell:

  mingw-get install msys-libregex msys-libintl msys-libopenssl
  mingw-get upgrade msys-libregex msys-libintl msys-libopenssl

Proceed as follows to build Net-SNMP:

1. Configure net-snmp using the configure flags as shown:

	BASEDIR=c:/usr

	./configure --prefix="$BASEDIR" \
		--with-mibdirs="$BASEDIR/share/snmp/mibs" \
	--with-mib-modules="agentx disman/event-mib winExtDLL examples/example"\
        --disable-embedded-perl --without-perl-modules \

   If you want to use IPv6 transports, add:
	--enable-ipv6 --with-transports="TCPIPv6 UDPIPv6"

   Note: while the Net-SNMP implementation of the host resources MIB is not
   supported when using MinGW, winExtDLL is supported. Via winExtDLL you can
   use Microsoft's implementation of the host resources MIB.

2. Type "make" to compile the package.

3. Type "make install" to install the package.

4. If the folder that Net-SNMP was installed to is ever changed, modify the
   system environment variables or registry keys as explained in the
   'Configuration_Overview.html' file located in win32/dist/htmlhelp.

***************************************************************************
*
* Mingw-w64 - Building
*
***************************************************************************

MSYS2 and Mingw-w64 can be installed as follows:
1. Download the MSYS2 installer from https://www.msys2.org/.
2. Run the MSYS2 installer.
3. Open an MSYS2 shell.
4. Run pacman -S make diffutils
5. On a 32-bit system, run
   pacman -S mingw-w64-i686-gcc mingw-w64-i686-openssl
6. On a 64-bit system, run
   pacman -S mingw-w64-x86_64-gcc mingw-w64-x86_64-openssl

Do not try to make the MinGW64 gcc compiler to use the MSYS2 openssl-devel
headers by adding /usr/include to the include path because this will trigger
plenty of complaints about redefined macros and structures.

***************************************************************************
*
* Building the Windows Net-SNMP Installer
*
***************************************************************************

Proceed as follows:
 1. Uninstall Net-SNMP.
 2. Remove the C:\usr directory completely.
 3. Open a command prompt
 4. Run the Microsoft Visual Studio vcvarsall.bat script.
 5. Change the current working directory to the Net-SNMP win32\dist directory.
 6. Run the .\build-binary.bat script.
 7. Copy the net-snmp-${version}.x86.exe installer to the desired location.

***************************************************************************
*
* Configuring Net-SNMP
*
***************************************************************************

Online documentation is available from the Net-SNMP home page at:

http://www.net-snmp.org/docs/

All configuration files should be placed in the INSTALL_BASE\etc\snmp folder.
The INSTALL_BASE folder is defined in the win32\net-snmp\net-snmp-config.h
file.  For example, c:\usr\etc\snmp.

Included is a Perl script called snmpconf which can be used to create
configuration files.  Full documentation on using snmpconf is available from the
Net-SNMP web site at the above link.

To run snmpconf, first modify snmpconf.bat located in the bin folder where
Net-SNMP is installed.  Modify the set MYPERLPROGRAM= line to contain the full
path to the snmpconf Perl script.  For example:

  set MYPERLPROGRAM=c:\usr\bin\snmpconf

You can now run snmpconf using the standard command line such as:

  snmpconf -i

For detailed information on using environment variables and the registry to
configure Net-SNMP, see the 'Configuration_Overview.html' file in
win32/dist/htmlhelp.


***************************************************************************
*
* How to Register the Net-SNMP Agent and Trap Daemon as Windows services
*
***************************************************************************

The Agent (snmpd.exe) and trap daemon (snmptrapd.exe) can be run as a service
under Windows operating systems that have the Service Control Manager (SCM)
(Services Control Panel).  This includes Windows NT, 2000, XP and 2003.
Windows 9x/Me do not have the SCM.

To allow snmpd.exe or snmptrapd.exe to run as a service, the programs need
to be registered with the SCM.  This is done by running the program once with
the -register command line switch from a command prompt.

If Net-SNMP was installed using the binary available from the Net-SNMP web site,
there will be shortcuts in the Start menu for registering and unregistering the
agent and snmptrapd.

The synopsis for registering snmpd as a Windows service is:

  snmpd -register [OPTIONS] [LISTENING ADDRESSES]

The synopsis for registering snmptrapd as a Windows service is:

  snmptrapd -register [OPTIONS] [LISTENING ADDRESSES]

After registration, the services 'Net-SNMP Agent' and 'Net-SNMP Trap Handler'
will be available in the SCM.  The services can be started and stopped using
the SCM (Services Control Panel) or from the command prompt using:

 net start "Net-SNMP Agent"
 net start "Net-SNMP Trap Handler"

and

 net stop "Net-SNMP Agent"
 net stop "Net-SNMP Trap Handler"

If any command line options are specified after the -register option, they
will be included when the service starts.  For example, to register the
snmptrapd daemon and enable logging of traps to c:\usr\log\snmptrapd.log,
enter the following command line:

 snmptrapd -register -Lf c:/usr/log/snmptrapd.log

Note:  Use Unix style slashes (/) for all paths.

For a complete list of command line options, consult the man pages, or use
the -h switch:

 snmpd -h
 snmptrapd -h

Notes: -H will display all available snmpd.conf, snmptrapd.conf and snmp.conf
       configuration file options, not the command line options.

       Like all Net-SNMP applications, snmpd and snmptrapd will use the
       SNMPCONFPATH and SNMPSHAREPATH environment variables when run as a
       service.  The registry is the recommended method for defining these
       variables due to a limitation in the Windows Service Control Manager
       (SCM).  When running as a service, if any system environment variables
       are changed, the system will need to be rebooted to allow the services
       to access the changed environment variables (see Microsoft knowledge
       base article  821761).  Therefore, when running snmpd or snmptrapd as
       a service, if SNMPCONFPATH or SNMPSHAREPATH is changed, a reboot will
       be required after setting the environment variables, otherwise the
       services may fail to start.  Using the registry to store the environment
       variables eliminates this problem.  See the 'Configuration_Overview.html'
       file in win32/dist/htmlhelp for more information on using the registry.


Unregistering the services
--------------------------

To un-register the services, use the command line switch -unregister.  For
example:

 snmpd -unregister

 snmptrapd -unregister

Note:  Be sure to have all Service Control Panel windows closed when
       unregistering, otherwise a reboot may be required to complete
       the removal.


Modifying the services
----------------------

To change the parameters that the SCM passes to snmpd or snmptrapd, the
service must be unregistered, and then re-registered with the new options.

For example, to change the parameters that SCM passes to snmpd, open a
command prompt window, CD to the directory where the snmpd program is located
(unless it is already in your PATH), identify the full set of parameters you
desire, then type these two commands:

 snmpd -unregister
 snmpd -register [OPTIONS] [LISTENING ADDRESSES]

Note:  Be sure to have all Service Control Panel windows closed when
       unregistering, otherwise a reboot may be required to complete
       the removal.


Registry Information
--------------------

Warning:  Improper use of the registry editor can damage to your operating
          system and should only be used by experienced users.

The following registry keys are used by snmpd and snmptrapd:

HKLM\SYSTEM\CurrentControlSet\Services\Net-SNMP Agent
HKLM\SYSTEM\CurrentControlSet\Services\Net-SNMP Trap Handler

Each command line option specified when regsitering the service will be added
to the Parameters registry subkey for the service as a ParamX REG_SZ value
where X starts at 1 and increments for each additional command line option.
For example, '-Lf c:/usr/log/snmptrapd.log' would be:

 HKLM\SYSTEM\CurrentControlSet\Services\
   Net-SNMP Trap Handler\Parameters\Param1 -Lf

 HKLM\SYSTEM\CurrentControlSet\Services\
   Net-SNMP Trap Handler\Parameters\Param2 c:/usr/log/snmptrapd.log

To add additional command line switches or modify the existing ones, it is
recommended to unregister and re-register the services with the new command
line options.  It is also possible to directly add or modify the ParamX values
in the registry.

Note:  The Parameters key is only created when there is at least one command
       line option specified when registering the service so it may need to be
       manually added if modifying using the registry editor.


***************************************************************************
*
* Notes on SET support for WIN32 ports
*
***************************************************************************

Requirements:

  Windows NT/2000/XP or later: Requires Windows NT 4.0 SP4 or later.
  Windows 95/98/Me: Requires Windows 98 or later.

Windows support for SET on following groups:

interfaces:
----------
ifAdminStatus is read-write. Status can be set with either 'up' or
'down'. (IE, 'testing' status is not supported.)


ip group:
--------
Scalar objects:
ipForwarding:Currently windows supports only ON->OFF (IE,
enable->disable). For any other value, it returns with failure.

ipDefaultTTL: Supports value greater than or equal to 0.

Table objects:
-------------
1. ipRouteTable:
   ------------
route_write.c implements this.

ipRouteDest: Setting this value, updates row with new ipRouteDest and all other
             entries will be same as old row.
    EX:
    Consider there is an entry with ipRouteDest = 10.0.0.20
    Request, snmpset localhost private ip.ipRouteTable.ipRouteEntry.ipRouteDest.10.0.0.20 -a 10.0.0.16
    Updates that row with ipRouteDest = 10.0.0.16

ipRouteIfIndex:Write supported.

ipRouteMetric1: Supports value greater than or equal to -1

ipRouteMetric2, ipRouteMetric3, ipRouteMetric4, ipRouteMetric5: Even though
		call returns with success, Windows doesn't change these (as
		these are not used in Windows)

ipRouteNextHop: Write supported.

ipRouteType: Write Supported. If value is 2, IE 'invalid', it deletes the entry.

ipRouteAge: Whenever any row is updated this will be automatically reset.

ipRouteMask: Write Supported.

Creation of ipRouteTable row:
-----------------------------
snmpset request for non existent OID with ipRouteIfIndex, ipRouteMetric1,
ipRouteNextHop and ipRouteMask varbinds, creates a row.

snmpset with create option is not supported, as row creation requires
ipRouteIfIndex, ipRouteMetric1, ipRouteNextHop and ipRouteMask  in a single
request.

Example to create a row:
-----------------------
Consider there is no entry for 10.0.0.18

snmpset localhost private ip.ipRouteTable.ipRouteEntry.ipRouteIfIndex.10.0.0.18 i 2 4.21.1.ipRouteMask.10.0.0.18 a 255.255.255.255 4.21.1.ipRouteNextHop.10.0.0.0 a 10.0.0.0 4.21.1.ipRouteMetric1.10.0.0.18 i 1

If ipRouteIfIndex is valid then creates row with:
ipRouteIfIndex = 2
ipRouteMask = 255.255.255.255
ipRouteNextHop = 10.0.0.0
ipRouteMetric1 = 1

2. ipNetToMediaTable:
--------------------
ipNetToMediaIfIndex: write supported
ipNetToMediaPhysAddress: write supported
ipNetToMediaNetAddress: write supported
ipNetToMediaType: write supported, setting with value 2, deletes the row.

Creation of row:
--------------------
snmpset request for non existent OID with ipNetToMediaPhysAddress varbind
creates a row.

snmpset with create option is not supported, as row creation requires
ipNetToMediaPhysAddress in a request
request.

Example to create a row:
-----------------------
Consider there is no entry for 10.0.0.32

snmpset localhost private ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaPhysAddress.2.10.0.0.32 x efcd12130103

If ipNetToMediaIfIndex is valid then creates row with:
ipNetToMediaIfIndex = 2
ipNetToMediaPhysAddress = ef:cd:12:12:01:03
ipNetToMediaNetAddress = 10.0.0.32
ipNetToMediaType = 4

TCP:
---
tcpConnState of tcpConnTable is writable and the only value which may
be set by a management station is deleteTCB(12)


***************************************************************************
*
* Notes on preprocessor defines for Microsoft Visual Studio, MinGW and Cygwin
*
***************************************************************************

When adding Windows specific code, proceed as follows:
- Add a configure test in the appropriate file under configure.d for MinGW
  and Cygwin.
- Add the symbol defined by the configure test to
  win32/net-snmp/net-snmp-config.h and also to
  win32/net-snmp/net-snmp-config.h.in. If the feature is supported by
  Microsoft visual Studio, define the symbol. Otherwise undefine it.

Try to avoid to add #ifdef's that use the WIN32, _MSC_VER, mingw32 and/or
cygwin macros. These macros are defined as follows:

Define:          Description:
-------          ------------
_WIN32           Defined by Microsoft Visual Studio, MinGW and Mingw-w64.

_WIN64           Defined by Microsoft Visual Studio and Mingw-w64 when
                 generating 64-bit code.

_MSC_VER         Defined by Microsoft Visual Studio only

__MINGW32__      Defined by MinGW and Mingw-w64

__MINGW64__      Defined by Mingw-w64 only

cygwin           Defined by Cygwin only


***************************************************************************
*
* Acknowledgements
*
***************************************************************************

These people are known to have contributed to one or more of
the Win32 platform ports.  If you have, and your name is not here,
please accept our apologies, and tell us so we can add your name.

David Perkins, Joe Marzot, Wes Hardaker, Niels Baggesen, Dave Shield,
Robert Story, Suvrit Sra, Mike Slifcak, Latha Prabhu, Nikolai Devereaux,
Alex Burger, Bernhard Penz, Andy Smith and Bart Van Assche.