Version 4.21 of the Extensible SNMP Agent now runs on the following operating systems and versions:

• HP-UX 11iv2 PA-RISC
• HP-UX 11iv3 PA-RISC and Itanium
• Solaris 5.10

Version 4.20 of the Extensible SNMP Agent includes the following features:

• The Extensible SNMP Agent now includes the SNMP EMANATE Agent 15.3 version, which supports SNMPv3 functionality.
• The EMANATE architecture provides the following benefits:
  • A master-agent and sub-agent concept where the SNMP protocol is implemented in the master agent, and the sub-agents implement the (Master Information Base) MIB. The master agent supports dynamic registration and deregistration of any MIBs supported by sub-agents.
  • You can extend the agent's MIB instrumentation in the following ways:
    • Purchase third party EMANATE sub-agents
    • Develop a sub-agent using the EMANATE Sub-Agent Development Kit (SADK) from SNMP Research.
    • Configure the extensible sub-agent to implement its own, new MIB. This is particularly useful if rapid development is important.
  • The protocol stack, which resides in the master agent (snmpdm), provides support for the SNMPv1, SNMPv2c, and SNMPv3 protocols.
  • You can configure multiple instances of the extensible sub-agent (extsubagt) each with its own, separate snmpd.extend file. This feature is designed to allow different entities to provide new instrumentation without the need to share a single snmpd.extend file.
• The Extensible SNMP Agent includes the extended sub-agent (extsubagt) which allows users to extend the MIBs supported by the master agent (snmpdm), the Mib-II agent (mib2agt) and the HP-UNIX agent (hp_unixagt). The extended sub-agent allows the following actions:
  • You can add your own MIB objects to the agent with or without programming.
  • You can configure the agent to notify the manager by sending traps.
  • You can override objects defined by other sub-agents.

  The objects you define can be configured to manage an application or device, or to send events. To use the extended sub-agent, you need to have a good knowledge of SNMP. For example, the new extended sub-agent allows you to add your own objects by defining a new MIB sub-tree in the MIB configuration file.

• Both the scalar and table file objects have the same data format in the file containing object instances (TOKENS)
• If an object is "set", the data value specified is always stored within double quotes for the following data types: OCTETSTR, DISPLAYSTR, OPAQUE and PHYSADDR.
• Double quote(s) in the data field are treated as a special character in the shell and stored with a preceding backslash for the following data types: OCTETSTR, DISPLAYSTR, OPAQUE and PHYSADDR.
• All other data types are stored in their original format
• For file-oriented MIB objects, the value returned is based on the first token in the file; the value is not based on the entire file
• The behaviour of the lexical analyzer, which parses the user-specified file, is very similar to the K-shell (ksh)
• If the Extensible SNMP Agent finds extra tokens in a row, it ignores the extra tokens and logs an error in snmpd.log
• Comments can start from any column and any line and are specified using a '#'
• Comments in between tokens are allowed; if the comment starts between tokens, the rest of the line (starting from '#') is treated as a comment
• Token values for both scalar and table objects can now be extended to a new line with a back slash character (\)
• Columns can be extended to a new line using the backslash (\) escape character
• Comments or white spaces within quotes ("") are treated as a token value
• File-table tokens from previous versions of the Exensible SNMP Agent are supported
• Leading and trailing quotes (") are allowed
• The first element of a table of tokens can be used as a token for scalar objects.
• The data value received in a get request is always the same as the data value sent while setting a file object.
• The number of bytes received in a data value for a get request is the same as number of bytes sent in a data value in a set request for string data types.
• Now, all the data types can be represented in three different formats where, in the examples below, characters enclosed in square brackets ([ ]) represent a wildcard and all tokens are converted to decimal before sent to the manager. The three data-type formats are:
  • Hexadecimal: 0x[0-f]
  • Octal: \[0-7]
  • Decimal: [0-9]
• If a row has less columns than defined in the MIB, the row is not evaluated. If the row has more columns than defined in the MIB, the extra columns are ignored. Errors are logged in the log file snmpd.log.
• Integer and counter data types can now be represented in any of the three allowed formats (hexadecimal, octal, or decimal). They should be represented only in any one format. Incorrectly specified values are discarded and an error returned. If the value range exceeds INT_MAX or INT_MIN, then INT_MAX and INT_MIN will be returned respectively. Note that a minus sign (-) is not allowed for counter data types.
• Ipaddr can have up to four parts with each part separated by a dot. Each part should have the range 0-256 and can be represented in any of the allowed formats (hexadecimal, octal, or decimal). Ipaddr can not be specified as a host name.

• String types can be a mixture of all allowed data formats (hexadecimal, octal, and decimal) but are converted back to the binary before being sent to the manager.

  Note that hexadecimal data is represented in the 2-byte format; octal data is represented in the 1-3 byte format. Note, too, that for data in the octal format, each character must be preceded by the backslash (\); for data in the hexadecimal format, 2 bytes will be taken for each character until a non-hexadecimal byte is encountered, for example:
  abc0x111213\101 is converted as abcabca

• In the Object Identifier (OID), each part is separated by a dot and each part is greater than zero. OID types may begin with either a dot or a number. Each part of the OID type may be represented in any of the three allowed formats (hexadecimal, octal, or decimal).
• The Extensible SNMP Agent on Solaris contains a Native Adapter Agent (naaagt), which is a sub-agent of SNMP Research's EMANATE master agent. naaagt registers itself with the EMANATE master agent for the object tree specified in $OVCONF/naa.cnf. On startup, naaagt reads the configuration file /etc/SnmpAgent.d/naa.cnf. The naa.cnf file specifies an object ID (OID) for each object to be registered. Each OID refers to the subtrees which naaagt registers with the EMANATE master agent.
• The PIPE TIMEOUT can be configured using the environment variable EA_PIPE_TIMEOUT.
• The file-cmd timeout value can be configured using the environment variable EA_CMD_TIMEOUT.

Before installing the Extensible SNMP Agent, make sure that your system meets the following minimum requirements:

• HP9000 700 and 800 series
• Sun Sparc systems
• K-class, T-class, etc. series

Before installing the Extensible SNMP Agent, make sure that your system meets the following minimum requirements for operating system, platform, and compatibility:

• HP-UX
  • PA-RISC: 11.00, 11.11, 11iv2 and 11iv3
  • Itanium: 11iv2 and 11iv3
• Solaris 2.8, 2.9, and 2.10

Before installing the Extensible SNMP Agent, make sure that your system meets the following minimum requirements for free and available disk space:

• 10 Mbytes of disk space is required on all platforms

To remove the Extensible SNMP Agent, perform the following steps:

1. Log in as root to the workstation from which you want to remove the Extensible SNMP Agent and open a command shell.
2. Run the following command to remove the Extensible SNMP Agent: /opt/OV/ExtAgt/remove
3. The removal process prompts you for an answer to the following questions, where the name of the bundle depends on the installed platform (Itanium, PA-RISC, etc.):
   • Remove bundle SNMPEAgntHPUX11IAx? [y|n] (y). Enter: Y (Yes)
   • Remove bundle SNMPEAgntHP11IAman? [y|n] (y). Enter Y (Yes) or N (No)
     Note that if you do not want to remove the manpages now, enter N (No) and remove them later.
   • Do you wish to continue with this removal? (y|n). Enter Y (Yes) to continue the removal process; enter N (No) to cancel the removal process and return to the command-line prompt.
4. If you enter Y (Yes) to start the removal process, the installation completes with one of the following status messages:
   • Product was successfully removed
   • Your removal has been stopped by a signal
     For more information about errors that occur during the removal process, check for entries in the log file /var/adm/sw/swagent.log.
     
   • Errors have been encountered in this removal
     For more information about errors that occur during the removal process, check for entries in the log file /var/adm/sw/swagent.log.