30.01.2013 Views

DCP Series Telcon Message Manual - Public Support Login - Unisys

DCP Series Telcon Message Manual - Public Support Login - Unisys

DCP Series Telcon Message Manual - Public Support Login - Unisys

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Event 11 ILM EVENT<br />

SNMP 121 No transport for trap<br />

Description: The SNMP Agent has a Trap PDU to send to a management station, but<br />

there is no UDP transport path currently available to output it. The Trap PDU is<br />

discarded.<br />

Action: Because the different components of ENS initialize asynchronously, this<br />

CENLOG may normally occur once when the ILM containing the SNMP Agent is<br />

initialized. If this CENLOG occurs at other times, it may indicate that the SNMP Agent<br />

has lost its previously available UDP transport path. Look for other symptoms of<br />

improper operation, such as the management station loosing contact with the SNMP<br />

Agent.<br />

SNMP 122 Not SNMPv1 msg<br />

Description: A PDU was received which is not SNMP version 1. The SNMP Agent<br />

does not support SNMPv2 PDUs. The PDU is discarded.<br />

Action: Single occurrences can be ignored. If this CENLOG occurs repeatedly, an<br />

SNMP trace with TYPE=M can be used to capture the offending PDU.<br />

SNMP 123 Too many subid's in OID<br />

Description: The SNMP Agent encountered an ASN.1 object identifier which either<br />

contained too many sub-identifiers, or a sub-identifier had too large a value. The<br />

current limits are up to 96 sub-identifiers in an object identifier up to 65535. The PDU<br />

is discarded.<br />

Action: An SNMP trace with TYPE=M can be used to capture the offending PDU.<br />

SNMP 124 Trap not OID<br />

Description: An internal error has been detected when attempting to build a Trap<br />

PDU where the supplemental information was not an object identifier.<br />

Action: Single occurrences can be ignored. If this CENLOG occurs repeatedly, an<br />

SNMP trace with TYPE=M can be used to capture the offending Request PDU.<br />

SNMP 127 Cannot truncate response<br />

Description: The SNMP Agent attempted to generate a Response PDU which<br />

exceeded the maximum PDU size. Under the rules of SNMP version 1, a truncated<br />

response is not allowed. The Response PDU is discarded.<br />

Action: Single occurrences can be ignored. If this CENLOG occurs repeatedly, an<br />

SNMP trace with TYPE=M can be used to capture the offending Response PDU.<br />

6–94 7436 0728–303

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!