16. SNMP
461
Response messages
Table 16-26:
List of response messages for the snmp rwalk command
Notes
If there are too many interfaces on the target Switch, it takes time for searching IP-related MIB
information, and a timeout might occur. If that happens, use the
snmp
rget
command to acquire
the information, or use the
snmp
rgetnext
command to set the instance value, and then acquire the
information.
Message
Description
<SNMP agent IP address>
: host unknown.
An invalid SNMP agent address was specified.
Cannot translate variable class:
<MIB Object Name>
The object name
<MIB Object Name>
is invalid.
Error code set in packet - General error:
<Number>
.
A response from the applicable SNMP agent indicating that the
specified object ID is being managed but the MIB value could
not be acquired correctly was received. The object ID specified
at the following position could not be acquired:
<Number>
.
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.
Содержание AX6300S series
Страница 4: ......
Страница 10: ......
Страница 16: ......
Страница 24: ......
Страница 25: ...9 PART 2 Filters Chapter 2 Filters show access filter clear access filter ...
Страница 34: ......
Страница 49: ...3 Access List Logging 33 Notes None ...
Страница 80: ...4 QoS 64 Notes None ...
Страница 112: ......
Страница 148: ......
Страница 202: ......
Страница 242: ......
Страница 264: ......
Страница 294: ......
Страница 304: ......
Страница 332: ......
Страница 377: ...12 VRRP 361 Notes None ...
Страница 378: ......
Страница 388: ...13 IEEE 802 3ah UDLD 372 file in advance if necessary ...
Страница 390: ......
Страница 406: ......
Страница 436: ...15 CFM 420 Notes None ...
Страница 440: ...15 CFM 424 Notes None ...
Страница 466: ...16 SNMP 450 appears and the MIB cannot be acquired ...
Страница 483: ...467 Chapter 17 sFlow show sflow clear sflow statistics restart sflow dump sflow ...
Страница 490: ......
Страница 497: ...18 LLDP 481 Notes None ...
Страница 505: ...489 Chapter 19 OADP show oadp show oadp statistics clear oadp clear oadp statistics restart oadp dump protocols oadp ...
Страница 514: ...19 OADP 498 Notes None OADP is not configured OADP has not been configured Check the configuration Message Description ...
Страница 516: ...19 OADP 500 Notes None OADP is not configured OADP has not been configured Check the configuration Message Description ...
Страница 520: ......