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.

SNMP 117 Msg before transport ready<br />

Event 11 ILM EVENT<br />

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

is no UDP transport path currently available to output it. The PDU is 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 118 Couldn't get buffer for ssssssss<br />

Description: An ILM buffer could not be obtained to contain the structure indicated<br />

by ssssssss.<br />

Variable: ssssssss The type of internal structure which could not be allocated.<br />

Action: This CENLOG indicates a tight memory situation in the ILM. If the ILM is not<br />

currently under heavy load, then an internal error may have occurred which<br />

consumed a lot of memory, and the ILM needs to be dumped.<br />

SNMP 119 No room for CDS header<br />

Description: The SNMP Agent did not have enough room at the beginning of a buffer<br />

to put a header on a PDU to a management station. The PDU is discarded.<br />

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

the ILM as close as possible to an occurrence.<br />

SNMP 120 Not my CIM msg: ssssssss<br />

Description: An internal error has occurred between the SNMP Agent and CIM-ILM.<br />

Variable: ssssssss A more detailed description of the type of error.<br />

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

7436 0728–303 6–93

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

Saved successfully!

Ooh no, something went wrong!