16. SNMP
443
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 IP-related MIB
information, and a timeout might occur. If that happens, use the
snmp
get
command to acquire
the information, or use the
snmp
getnext
command to set the instance value and then acquire
the 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.
make_obj_id_from_dot, bad character : x,y,z
An object ID specified in dot notation contains invalid
characters, such as x, y, and z.
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
Summary of Contents for AX6300S series
Page 4: ......
Page 10: ......
Page 16: ......
Page 24: ......
Page 25: ...9 PART 2 Filters Chapter 2 Filters show access filter clear access filter ...
Page 34: ......
Page 49: ...3 Access List Logging 33 Notes None ...
Page 80: ...4 QoS 64 Notes None ...
Page 112: ......
Page 148: ......
Page 202: ......
Page 242: ......
Page 264: ......
Page 294: ......
Page 304: ......
Page 332: ......
Page 377: ...12 VRRP 361 Notes None ...
Page 378: ......
Page 388: ...13 IEEE 802 3ah UDLD 372 file in advance if necessary ...
Page 390: ......
Page 406: ......
Page 436: ...15 CFM 420 Notes None ...
Page 440: ...15 CFM 424 Notes None ...
Page 466: ...16 SNMP 450 appears and the MIB cannot be acquired ...
Page 483: ...467 Chapter 17 sFlow show sflow clear sflow statistics restart sflow dump sflow ...
Page 490: ......
Page 497: ...18 LLDP 481 Notes None ...
Page 520: ......