SNMP Daemon Implementation Restrictions

The current implementation of the Simple Network Management Protocol (SNMP) agent does not have:

• User interface for proxy agent support
• Nontrivial authentication support.

Not all values defined in RFC 1213 are supported, as illustrated in the following note:

Note: A set request for ipRouteType 2 (invalid) causes deletion of a route. A get request will never return this value for an existing route.

The following implementation restrictions should be observed:

• An interface must be enabled by a locally issued ifconfig command before it can be enabled or disabled by the ifAdminStatus variable. There is no way to associate an Internet Protocol (IP) address with an interface except with a locally issued ifconfig command.
• The snmpd agent does not provide a way to alter the IP address associated with an interface adapter. This must be done with a locally issued ifconfig command.
• The maximum message size that can be sent is 9KB (9216 bytes). The maximum message that can be received is 40KB (40960 bytes).

If you set the value of the MIB variable ipForwarding to 1, indicating that the TCP/IP kernel should forward packets, the snmpd agent performs some interface checks before it will allow the set operation to succeed. If there is more than one active interface, then the MIB variable ipForwarding is set to 1 and the Transmission Control Protocol/Internet Protocol (TCP/IP) kernel configurable option ipforwarding is set to 1. Otherwise, the snmpd agent does not perform the set operation and an error badValue is returned.