ELS Messages for Simple Network Management Protocol (SNMP)
- Level:
- P-TRACE
- Short Syntax:
- SNMP.001 rcvd pkt frm hst source_address
- Long Syntax:
- SNMP.001 received packet from host source_address
- Description:
- This message is generated for each SNMP packet received from
a remote host.
- Level:
- P-TRACE
- Short Syntax:
- SNMP.002 snt pkt to hst dest_address
- Long Syntax:
- SNMP.002 sent packet to host dest_address
- Description:
- This message is generated for each SNMP packet sent to a
remote host.
- Level:
- UE-ERROR
- Short Syntax:
- SNMP.003 rcvd non-SNMP pkt frm hst source_address
(err= value
)
- Long Syntax:
- SNMP.003 received non-SNMP packet from host source_address
(error code = value
)
- Description:
- This message is generated by a first-level reasonableness
check of an incoming SNMP packet. The error codes have
the following meanings:
1 - packet does not begin with SEQUENCE (0x30)
2 - packet sequence length too small
3 - packet sequence length improperly encoded (in one byte)
4 - first packet field not an ASN.1 INTEGER
5 - packet sequence length improperly encoded (in two bytes)
6 - first packet field not an ASN.1 INTEGER
7 - some other error was detected
- Cause:
- Another node on the network sent an improperly formed SNMP
packet to the router.
- Action:
- Examine the remote node, specified in the error message, for
errors.
node, get a line trace containing the bad packet. Be certain
to report the correct error code to engineering.
- Level:
- UE-ERROR
- Short Syntax:
- SNMP.004 bad ver version
frm hst source_address
- Long Syntax:
- SNMP.004 bad version number version
from host source_address
- Description:
- This message indicates that an SNMP packet contained an
incorrect version number.
- Cause:
- Either the router or the Network Manager is running an
incompatible version.
- Action:
- Update (or back out) one version of SNMP.
- Cause:
- A bad packet slipped through the first-level error checks.
- Action:
- Check the network for wild packets.
- Level:
- U-TRACE
- Short Syntax:
- SNMP.005 no access: comm " community
", hst source_address
- Long Syntax:
- SNMP.005 no access to community " community
" from host source_address
- Description:
- This message indicates that an SNMP request from a remote
host specified a community which does not exist or a
community which did not list that host's IP address as
acceptable.
- Cause:
- The remote host is using the wrong community name.
- Action:
- Update the remote hosts Network Manager.
- Cause:
- The defined community in the router is incorrect.
- Action:
- Correct the community name or add the remote host's IP
address to the community's list.
- Level:
- UE-ERROR
- Short Syntax:
- SNMP.006 bad appl type appl_type
frm hst source_address
- Long Syntax:
- SNMP.006 bad application type appl_type
from host source_address
- Description:
- This message indicates that an SNMP packet had a bad
application type. That is, it was not a GET, GETNEXT
or SET request.
- Cause:
- The remote host is in error (perhaps sending response
packets).
- Action:
- Check the remote host.
- Cause:
- A bad packet slipped through the first-level error checks.
- Action:
- Check the network for wild packets.
- Level:
- UI-ERROR
- Class:
- OOM
- Short Syntax:
- SNMP.007 no free pkr bfr
- Long Syntax:
- SNMP.007 no packet buffer available
- Description:
- This message is generated when SNMP cannot allocate a
packet in which to construct an SNMP response.
dumps the request packet. If this happens a lot and
the customer has an HKME, upgrade it to 1 meg. If it
is already 1 meg, there may be a serious problem.
- Level:
- U-TRACE
- Short Syntax:
- SNMP.008 R/O access for SET: hst source_address
, comm " community
"
- Long Syntax:
- SNMP.008 SET request from host source_address
has read-only access on community " community
"
- Description:
- This message indicates that a SET request came in on a
community which only provides read-only access to the MIB.
- Action:
- Provide a community which allows sets or get the remote
host to stop sending SET requests.
- Level:
- UI-ERROR
- Class:
- OOM
- Short Syntax:
- SNMP.009 TRAP: no free pkt bfr
- Long Syntax:
- SNMP.009 TRAP: no free packer buffer available
- Description:
- This message is generated whenever SNMP cannot send an event
because it cannot allocate storage.
- Level:
- P-TRACE
- Class:
- FAKE
- Short Syntax:
- SNMP.010 FAKE: pkt dscrd frm hst source_address
- Long Syntax:
- SNMP.010 FAKE: packet discarded from host source_address
- Description:
- This message is generated by the SNMP fake-out routine.
- Cause:
- An SNMP packet arrived and the router does not have SNMP
support.
- Level:
- U-TRACE
- Class:
- FAKE
- Short Syntax:
- SNMP.011 FAKE: EGP neighbor IP_address
lost
- Long Syntax:
- SNMP.011 FAKE: EGP neighbor IP_address
lost
- Description:
- This message is generated by the SNMP, EGP neighbor loss
fake-out routine.
- Cause:
- EGP tried to generate a neighbor loss event but the router
does not have SNMP installed.
- Level:
- C-TRACE
- Short Syntax:
- SNMP.012 comm name
added
- Long Syntax:
- SNMP.012 community name
added
- Description:
- This message is generated by the SNMP configuration routine when
it reads a new community in from SRAM.
- Level:
- UE-ERROR
- Short Syntax:
- SNMP.013 rcvd non-SNMP pkt frm hst source_address
- Long Syntax:
- SNMP.013 received non-SNMP packet from host source_address
- Description:
- This message is generated by a reasonableness
check of an incoming SNMP packet. This check is done just before
processing the PDU.
- Cause:
- Another node on the network sent an improperly formed SNMP
packet to the router, and the packet slipped through the first level
error checks.
- Action:
- Examine the remote node, specified in the error message, for
errors.
node, get a line trace containing the bad packet.
Check the network for wild packets.
This error should not be detected at all. Earlier checks should always
catch this packet.
- Level:
- UE-ERROR
- Short Syntax:
- SNMP.014 bad ovarlen source_address
frm hst ovarlen
- Long Syntax:
- SNMP.014 length of variable to be sent out exceeds max length source_address
from host ovarlen
- Description:
- This message is generated by a length check on the variable
to be sent out.
- Cause:
- Another node on the network sent an improperly formed SNMP
packet to the router, and the packet slipped through the first level
error checks.
- Action:
- Examine the remote node, specified in the error message, for
errors.
node, get a line trace containing the bad packet.
Check the network for wild packets.
- Level:
- P-TRACE
- Short Syntax:
- SNMP.015 rcvd get-req pkt frm hst source_address
- Long Syntax:
- SNMP.015 received a get-request packet from host source_address
- Description:
- This message is generated for each SNMP packet received from
a remote host of the type get-request.
- Level:
- P-TRACE
- Short Syntax:
- SNMP.016 rcvd get-nxt pkt frm hst source_address
- Long Syntax:
- SNMP.016 received a get-next packet from host source_address
- Description:
- This message is generated for each SNMP packet received from
a remote host of the type get-next.
- Level:
- P-TRACE
- Short Syntax:
- SNMP.017 rcvd set-req pkt frm hst source_address
- Long Syntax:
- SNMP.017 received a set-request packet from host source_address
- Description:
- This message is generated for each SNMP packet received from
a remote host of the type set-request.
- Level:
- U-TRACE
- Short Syntax:
- SNMP.018 pkt frm hst : source_address
caused err typ toobig
- Long Syntax:
- SNMP.018 packet from host source_address
resulted in a pkt with error status: toobig
- Description:
- This message indicates that a packet was sent out with the error
status as too big as a result of the SNMP variable in question
not fitting the packet size.
- Action:
- Increase the packet-size.
- Level:
- U-TRACE
- Short Syntax:
- SNMP.019 pkt frm hst : source_address
caused err typ nosuchnam
- Long Syntax:
- SNMP.019 packet from host source_address
resulted in a pkt with error status: nosuchnam
- Description:
- This message indicates that a packet was sent out with the error
status as noSuchName as a result of the SNMP variable in question
not existing in the gateway or not in the view associated with
the specified community or the operation is a set on a read-only
variable.
- Action:
- Ensure that the requested variable exists in the gateway (also
possibly the particular instance of the variable), it is in the
requested view, the community has the correct access type and
the requested variable is writable if it is a set operation.
- Level:
- U-TRACE
- Short Syntax:
- SNMP.020 pkt frm hst : source_address
caused err typ badvalue
- Long Syntax:
- SNMP.020 packet from host source_address
resulted in a pkt with error status: badvalue
- Description:
- This message indicates that a packet was sent out with the error
status as badvalue as a result of trying to set a variable with a
wrong value specified in the SET request.
- Action:
- Ensure that the SET request from the remote host specifies a value
consistent with the ASN1 type of the value that it is attempting
to set.
- Level:
- UE-ERROR
- Short Syntax:
- SNMP.021 Pkt discd, inp buffs low, net Network ID
- Long Syntax:
- SNMP.021 Packet Discarded, input buffers are low, network Network ID
- Description:
- The input buffer pool of the incoming
SNMP packet fell below the low watermark. The router dropped the
SNMP packet to try to free up buffer space for other traffic.
- Cause:
- A burst of traffic overflowed the input buffers on an interface.
- Action:
- If this occurs regularly, you may have to increase the input
buffers of the interface indicated in the message.
- Panic
- nmnostor
- Short Syntax:
- SNMP: no storage for MIB
- Description:
- No storage was available to add an entry to the MIB.
- Panic
- nmitype
- Short Syntax:
- SNMP: interface type not defined for net
- Description:
- The structure that defines an interface does not define a
value for the MIB-II ifType variable.
- Action:
- Contact customer service for a new load. Do not try and
enable SNMP with this load.
- Panic
- snmpudperr
- Short Syntax:
- snmp udp port not avail
- Description:
- Another application registered previously with snmp's UDP port.
- Action:
- Contact customer service.