na.snmpv2 manual page
Table of Contents

NAME

na.snmpv2 - Simple Network Management Protocol - Version 2 proxy agent

DESCRIPTION

The SNMPv2 proxy agent allows a SunNet Manager user to manage SNMPv1 and SNMPv2 devices. na.snmpv2 can be used with the following SNMP schemas:

· Sun-supplied schema file. (See FILES)

· Schema file supplied by a vendor or other source.

· Schema file that you create from an enterprise MIB. (See
mib2schema(1) for more information.)

If no reporting interval is specified for requests, the proxy agent will report every 30 seconds.

OPTIONS

Management applications can specify a range of SNMP-related options when making a request to the SNMP proxy agent. For example, the schema name, read and write community strings, and request timeout can be sent with the request.

For requests that are sent from the SNM Console, the read and write community strings and request timeout are specified in the Properties window of the target device. In addition, the Options fields in the Data or Event Request Properties window and in the Set Tool window allow you to specify a community string for the request. The schema you choose for the request is also sent to the SNMP proxy as an optional argument.

For other management applications, optional request arguments are sent to the SNMP proxy with the netmgt_set_argument(3n) function. The SNMP proxy agent accepts the following request argument names:

na.snmpv2-read-community
na.snmpv2-write-community
na.snmpv2-schema
na.snmpv2-proxy-device
na.snmpv2-get-list
na.snmpv2-get-next-list
na.snmpv2-timeout

All these request arguments except for na.snmpv2-timeout are NETMGT_STRING argument type codes. na.snmpv2-timeout is a NETMGT_LONG argument type code. See the netmgt_set_argument(3n) man page for a description of how to set these arguments. For examples of how to set optional arguments, see Section 4.2, ``Optional Arguments,'' in Chapter 4, ``Requesting Data and Event Reports,'' in the Site/SunNet/Domain Manager Application and Agent Development Guide.

FILES

The proxy agent uses keywords in the /etc/opt/snm/snm.conf file for Solaris 2.x and in the /etc/snm.conf file for Solaris 1.x on the host running the proxy agent. /etc/opt/snm/snm.conf for Solaris 2.x or /etc/snm.conf for Solaris 1.x is required on the host running the proxy agent. See the snm.conf(5) man page.

snmp.schema(5) describes MIB I, as defined by RFC 1156. snmp-mibII.schema(5) describes MIB II, as defined by RFC 1213. sun-snmp.schema describes the MIB associated with the Sun-supplied SNMP agent and snmpv2d(8) for SPARC systems. This MIB is based on MIB II with SunOS-specific extensions.

NOTES

na.snmpv2 sends all SNMP requests to port 161.

na.snmpv2 usually accepts and displays table key components separated with a period (.). For example, an SNMP atTable key would look like ``1.1.129.144.40.245.'' The exception is where the key for a table in a schema is defined as type MAC_ADDRESS (that is, ``-K MAC_ADDRESS''). The key is then accepted and displayed in the standard, colon-separated hexadecimal format (for example, AA:00:04:00:63:20). Keys can be formatted in either MAC address format or standard dot notation, but not both at the same time. The proxy agent is able to handle a key with any number of components as long as the total key length is less than 128 octets.

ERRORS

attribute unavailable for set operation
The set could not be completed because the attribute was not available for set operations.

bad attribute type
An object attribute type received from the SNMP agent does not match the attribute type specified by the proxy agent schema. The rest of the message indicates the expected type and received type.

bad variable list: no object identifiers The request's optional argument ``na.snmpv2.get-list'' or ``na.snmpv2.get-next-list'' does not contain any object identifiers.

cannot create new subprocess; would exceed maximum: maximum The proxy agent cannot start a new request because creating a new subprocess would exceed the maximum number of proxy agent subprocesses allowed. Either terminate some requests and then resubmit the request, or modify the value associated with the ``na.snmpv2.max-subprocs'' keyword in /etc/opt/snm/snm.conf for Solaris 2.x and in /etc/snm.conf for Solaris 1.x. If you change the ``na.snmpv2.max-subprocs'' value, you must terminate all na.snmpv2 requests, kill all na.snmpv2 processes, and then restart the SNMP requests.

bad variable value
The requested specified an incorrect syntax or value for a set operation.

cannot dispatch request
The proxy cannot dispatch the request. The rest of the message indicates the cause of the failure.

cannot find default schema: "schema" in search path: "path" The proxy agent could not find the default schema in the schema search path specified by the ``na.snmpv2.schemas'' keyword in the /etc/opt/snm/snm.conf file for Solaris 2.x and in the /etc/snm.conf file for Solaris 1.x. Make sure that the default schema is in one of the directories in the schema search path.

cannot find group: "group" in schema: "schema" The proxy agent could not find the requested group in the specified schema. Make sure that the schemas used by the management application match the schemas used by the proxy agent.

cannot find group: "group" in default schema: "schema" The proxy agent could not find the requested group in the default schema. Make sure that the schemas used by the management application match the schemas used by the proxy agent.

cannot find schema: "schema" in search path: "path" The proxy agent could not find the specified schema in the schema search path specified by the ``na.snmpv2.schemas'' keyword in the /etc/opt/snm/snm.conf file for Solaris 2.x and in the /etc/snm.conf file for Solaris 1.x. Make sure the schema is in one of the directories in the schema search path.

cannot get sysUpTime
The proxy agent cannot get the variable sysUpTime from the SNMP agent.

cannot make request PDU
An error occurred building a request PDU.

cannot make request varbind list
An error occurred building a request variable binding list.

cannot open host file
An error occurred opening the file associated with the "na.snmpv2.hostfile" keyword in /etc/opt/snm/snm.conf for Solaris 2.x and /etc/snm.conf for Solaris 1.x.

cannot open schema file
An error occurred opening the proxy agent schema file.

cannot parse host file
The proxy agent was unable to parse the file associated with the ``na.snmpv2.hostfile'' keyword in /etc/opt/snm/snm.conf for Solaris 2.x and in /etc/snm.conf for Solaris 1.x.

cannot parse response PDU
An error occurred parsing a response PDU.

cannot parse schema file
The proxy agent could not parse the proxy agent schema file.

general error
A general error was received.

invalid table key: "key"; key must be in dot notation The requested key must be in standard dot notation, that is, decimal numbers separated by periods.

invalid table key: "key"; key must be in MAC address format The requested key must be in standard MAC address format, that is, hexadecimal numbers separated by colons. This error message only occurs for tables whose key is defined as type MAC_ADDRESS in the associated schema file.

missing attribute
an attribute is missing from the requested group.

no response from system
the SNMP agent on the target system does not respond to SNMP requests. This error might indicate that the SNMP agent is not running on the target system, the target system is down, or the network containing the target system is unreachable.

recvfrom(3n) failed
A recvfrom(3n) system call failed. The rest of the message indicates the cause of the failure.

request ID - response ID mismatch
The response ID does not match the request ID.

response too big
The agent could not fit the results of an operation into a single SNMP message. Split large groups or tables into smaller groups.

select(3C) failed
A select(3C) system call failed. The rest of the message indicates the cause of the failure.

string contains non-displayable characters A string contains non-displayable characters.

sysUpTime type bad
The variable sysUpTime received from the SNMP agent has the wrong data type.

unknown SNMP error
An unknown SNMP error was received.

variable is read only
The SNMP agent did not perform the set request because a variable to set may not be written.


Table of Contents