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 507 Encoding packet encoding type error (xxxx)<br />

Description: A response from the SMP contained an encoding type not known to<br />

MIBman.<br />

Variable: xxxx The encoding type that caused the error.<br />

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

message.<br />

SNMP 508 No SMP Reg Command was received<br />

Description: A Get Response was received from the SMP before a SMP REG was<br />

done.<br />

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

message.<br />

SNMP 509 Unknown message (xxxx), received from the ssssssss<br />

Description: An unknown command was received from the SNMP manager or the<br />

SMP. If the message came from the SNMP manager, probably the command is not<br />

supported by the SNMP Agent. If the message came from the SMP, probably the<br />

command is not supported by the SMP.<br />

Variables: xxxx The message type<br />

ssssssss The name of the entity that sent the message, for example the<br />

manager or the SMP.<br />

Action: If the message came from the SNMP Manager, check the message type.<br />

Currently the <strong>DCP</strong> only supports SNMPv1 commands. In either case, an SNMP trace<br />

with TYPE=LM can be used to capture the offending message.<br />

SNMP 510 Couldn't get a 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 that 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, an internal error may have occurred which consumed a<br />

lot of memory. Dump the ILM.<br />

6–102 7436 0728–303

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

Saved successfully!

Ooh no, something went wrong!