Alaxala AX6300S series, Руководство пользователя программного обеспечения

Страница: 468 / 522

16. SNMP
452
Notes
1. For five minutes immediately after the power is turned on or the
copy
command is used to
copy the backup configuration file to the startup configuration file, the
No response
message
appears because the SNMP agent is being initialized.
2. If there are too many interfaces on a Switch, it takes time for searching MIB information for
ipNetToMediaTable, and a timeout might occur. If that happens, use the
snmp getnext
command to acquire the ipNetToMediaTable information.
3. If the
snmp-server community
configuration command is not set, the
No response
message
appears and the MIB cannot be acquired.
Error code set in packet - No such variable name. Index:
<Number> .
A response from the applicable SNMP agent indicating that the
specified object ID is not managed was returned. The object ID
specified at the following position is not managed: <Number> .
The object ID specified at the following position is not
managed: <Number> .
Error code set in packet - Return packet too big. The response indicating that an attempt to return a MIB value
exceeding the allowable size was made in the applicable
SNMP agent was returned.
Error code set in packet - Unknown status code: <Code> An SNMP frame containing response status code <Code> ,
which is undefined (non-standard), was received.
error parsing packet. An SNMP frame in an invalid format was received.
error parsing pdu packet. A frame that contains an SNMP PDU frame format error was
received.
No ARP information available. There were no ARP table entries.
No response - retrying The command is being retried because there were no responses
from the applicable SNMP agent.
No response - try again. There were no responses from the applicable SNMP agent.
receive error. A receive error occurred.
request ID mismatch. Got: <ID1> , expected: <ID2> A frame whose request ID number of the SNMP frame is
<ID2> was expected, but an SNMP frame whose request ID
number is <ID1> was received. Alternatively, a timeout
occurred while searching the MIB.
unable to connect to socket. An attempt to send an SNMP frame was made, but failed.
Message Description