cc/td/doc/product/wanbu/mgx8850/13
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Message and Recovery Procedures

Message and Recovery Procedures

This chapter lists the error messages by facility. Within each facility, the messages are listed by severity levels 1 to 7, where 1 is the highest severity level and 7 is the lowest severity level. Each message is followed by an explanation and a recommended action.


Note The date/time stamp designation precedes every message; however, for the sake of simplifying this document, only the text of each message, alphabetized by category, is shown in this chapter.

Boot (BOOT) Messages

This section contains the boot (BOOT) messages.

Error Message   BOOT-4-SERIALHUNGHCR: Serial port is hung HCR wrong hcr=[dec]x.

Explanation   The serial port is hung (HCR is set wrong), resetting the serial device.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the Processor Switch Module (PXM) to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   BOOT-4-SERIALHUNGREAD: Serial port is hung read int. icr=[dec]x.

Explanation   The serial port is hung (read interrupt disabled), resetting the serial device.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   BOOT-4-SERIALHUNGWRITE: Serial port is hung write int. icr=[dec]x count=[dec].

Explanation   The serial port is hung (write interrupt disabled), resetting the serial device.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Cell Bus Controller (CBC) Messages

This section contains the Cell Bus Controller (CBC) messages.

Error Message   CBC-4-CBC_DRV_ERR1: Err1 : [chars] slot [dec] : [chars]

Explanation   Unknown/Invalid Board Id.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CBC-4-CBC_DRV_ERR2: Err2 : [chars] slot [dec] : [chars]

Explanation   The given CBC Slot is unmapped and invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CBC-4-CBC_DRV_ERR3: Err3 : [chars] slot [dec] : [chars]

Explanation   cbcIN(y/present deasserted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CBC-4-CBC_DRV_ERR4: Err4 : [chars] slot [dec] : [chars]

Explanation   Physical slot not configured to Logical slot.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CBC-4-CBC_DRV_ERR: Err : [chars] param-id [dec] : [chars]

Explanation   Unable to write to CBD chip.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CBC-4-CBC_UTIL_ERR: Err : [chars] params [dec][dec][dec][dec] : [chars]

Explanation   RAM access failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Channel Statistics Module (CHS) Messages

This section contains the Channel Statistics Module (CHS) messages.

Error Message   CHS-4-CHS_INIT_ERR: CHS : Task Init Failed

Explanation   Channel initialization failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Command Line Interface (CLI) Messages

This section contains the Command Line Interface (CLI) messages.

Error Message   CLI-7-CMDLOG: cliCmdLog: [chars]@[chars]: [chars]

Explanation   The above command was entered by the user via CLI.

Recommended Action   No action required.

Error Message   CLI-4-CLISMTERMD: cliSmtermd: [chars]: failed

Explanation   CLI API Error. A call to the above function failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CLI-7-CLITNLOG: cliTelnetd: client@[chars]: [chars]

Explanation   A telnet session was attempted by the user.

Recommended Action   No action required.

Error Message   CLI-5-AUTHENTICATION: [chars]@[chars]: [chars]

Explanation   Could not send Login/Logout SNMP trap for CLI session.

Recommended Action   No action required.

Error Message   CLI-5-TASKDELETEFAIL: [chars]: ssiTaskDelete[chars]: 0x[dec]ed for [dec] trials in [dec] seconds

Explanation   The task with given task id could not be deleted.

Recommended Action   No action required.

Error Message   CLI-5-GENERALWARNING: [chars]: [chars]: [chars]: [chars]

Explanation   Problems caused by routine calls that need attention.

Recommended Action   No action required.

Card Management Mode (CMM) Messages

This section contains the Card Management Mode (CMM) messages.

Error Message   CMM-4-INIT_ERROR_CMM: Init Error: [chars]

Explanation   CMM/VSM initialization error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CMM-4-GET_MSG_ERROR: Get Message: [chars]

Explanation   Error in receiving message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CMM-4-GET_EVENT_ERROR: Get Event: [chars] [dec]

Explanation   Error in receiving event.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CMM-5-UNKNOWN_MSG: UNknown message: [chars]

Explanation   Unknown message received.

Recommended Action   No action required.

Error Message   CMM-4-SEND_MSG_ERROR: Send Message failed: [chars]

Explanation   Error in sending a message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CMM-4-RCV_MSG_FAILED: Init Error: [chars]

Explanation   Error in receiving messages.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   CMM-5-INVALID_SLOT_NO: Invalid Slot Number [chars] [dec]

Explanation   The input parameter to this function was invalid.

Recommended Action   No action required.

Error Message   CMM-7-SLOT_NO_SET: updateSlotNum: Old S.N.= [dec] New S.N.=[dec]

Explanation   Slot number is successfully set.

Recommended Action   No action required.

Control Point Software (CNTP) Messages

This section contains the Control Point Software (CNTP) messages.

Error Message   CNTP-7-MSGSUBS: cntpMsgBufTake : ssiFrameBufferAlloc failed [dec] times.

Explanation   Attempt to allocate a buffer using ssiFrameBufferAlloc from the control point subsystem failed the specified number of times.

Recommended Action   No action required.

Database Manager (DBM) Messages

This section contains the Database Manager (DBM) messages.

Error Message   DBM-4-PARMINVALID: Parm [chars] value '0x[hex]' is invalid to [chars].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-PARMINVLENGTH: Parm [chars] invalid length of [dec] to [chars]. Max=[dec] Value='[chars]'

Explanation   API Software Error. The named parameter passed in as an argument to the named function either had a length of zero or exceeded the maximum value specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-PARMINVCHAR: Parm [chars] '[chars]' has invalid char of '[chars].

Explanation   API Software Error. The named parameter passed in as an argument to the named function had an invalid character in the string.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-PARMOUTOFRANGE: Parm [chars] '[dec]' is out of range [dec]-[dec] to [chars].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function is out of the specified range of values.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-PARMMAXEXCEEDED: Parm [chars] '[dec]' has exceeded max [dec] to [chars].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function exceeded maximum value specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-PARMRANGEINV: [chars] range [dec]-[dec] exceeds [chars] max [dec] to [chars].

Explanation   API Software Error. An invalid parameter range was specified for the name function. The starting number plus the number to do exceeds the total number available in the specified database object.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-STATEINVALID: EVENT_DUMP_TRACE 0 State '[chars]' for [chars] '[chars]' is invalid to [chars].

Explanation   API Software Error. The state for the specified database object was invalid for the named function. A call was made out of sequence or too soon to be serviced. Any previous database failures could cause this condition.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-NOTACTIVEUPDATE: Db [chars] update when card is not active in [chars].

Explanation   API Software Error. A database update operation was attempted for the named database when the card is not active. This happened in the named function. Updates can only be done on the active card.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-RAMACCESSFAIL: EVENT_DUMP_TRACE 0 Ram Table '[chars]' access to elmt [dec] failed in [chars].

Explanation   Unable to get RAM data for the specified table and specified element number in the named function. The element block pointer is invalid. There is no data block available for the element.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-TBLFUNCFAIL: EVENT_DUMP_TRACE 0 Db Table '[chars]' [chars] function failed. rc=[dec] Func=

Explanation   The specified callback function for the specified table failed with the return code specified. The function address which failed is also specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-NAMEDUPLICATE: Name '[chars]' is duplicate to [chars].

Explanation   A duplicate name was passed as an argument to the named function. That name has already been used.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-TBLNOTEXIST: Table [chars] does not exist for db [chars]. Add not allowed.

Explanation   The named table does not exist for the previously created named database. A table cannot be added to a previously registered database or once registration complete has been called.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-TBLCONFIGDIFF: Db config diff from disk. Field=[chars] Table=[chars].

Explanation   The configured size of the specified database table changed from the disk config without a version change. The database version must be upgraded to support the config change or the database must be deleted first.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-NOTSUPPORTED: [chars] operation is not supported in [chars].

Explanation   The named operation is not currently supported in the specified function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-TBLNOTREGSTR: EVENT_DUMP_TRACE 0 Table [chars] for db [chars] has not been registered.

Explanation   The specified table name has not been registered during the initialization of the software. The table exists in the current version of the database.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-5-NOUPDATETOCMT: No Updates to Db [chars] found to be committed in [chars].

Explanation   API Software Error. There are no updates to be committed to the specified database even though database commit has been called.

Recommended Action   No action required.

Error Message   DBM-4-SEMCREATEFAIL: Db [chars][chars] sem create failed in [chars]. errno=[hex].

Explanation   Unable to create the specified semaphore in the named function. It failed with the specified error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-SEMTAKEFAIL: Db [chars][chars] sem take failed in [chars]. rc=[dec] errno=[hex].

Explanation   Unable to take the specified semaphore for the specified database in the named function. It failed with the specified return code and error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-PORTCREATEFAIL: Db ipc port [dec] create failed in [chars]. rc=[dec] errno=[hex].

Explanation   Unable to create the specified pipc port in the named function. It failed with the specified return code and error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-IPCGETBUFFAIL: Db get ipc buffer failed in [chars]. size=[dec] rc=[dec] errno=[hex].

Explanation   Unable to get a pipc memory buffer. It failed with the specified return code and error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MSGSENDFAIL: Db [chars] send failed in [chars]. Type=[chars] rc=[dec] errno=[hex].

Explanation   Unable to send a pipc message of the specified type to other pxm card. It failed with the specified return code and error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MEMALLOCFAIL: Db [chars][chars] memory alloc failed in [chars]. errno=[hex].

Explanation   Unable to allocate the specified memory buffer for the specified database in the named function. It failed with the specified error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-TASKSPAWNFAIL: Db [chars] task [chars] failed in [chars]. rc=[dec] errno=[hex].

Explanation   Unable to spawn the specified task in the named function. It failed with the specified rc and error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-PMMFUNCFAIL: Db manager call to [chars] failed in [chars]. rc=[dec] errno=[hex].

Explanation   The specified PMM function call failed. It failed with the specified return code and error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-REGISTERFAIL: Db [chars] register [chars] failed in [chars].

Explanation   Unable to perform the specified operation to the disk db table for the specified database in the named function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-DISKOPFAIL: Db [chars] disk [chars] failed in [chars].

Explanation   Unable to perform the specified operation to the disk db table for the specified database in the named function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-SENDOPFAIL: Db [chars] send [chars] failed in [chars].

Explanation   Unable to perform the specified send operation for the specified database in the named function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-SYNCOPFAIL: Db [chars] sync [chars] failed in [chars].

Explanation   Unable to perform the specified sync operation for the specified database in the named function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-VEROPFAIL: Failed to [chars] version file for db '[chars]' in [chars].

Explanation   The specified operation on the version file for the specified disk database has failed in the named function. See previous event for detailed failure information and next event for error context.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MAPOPFAIL: Failed to [chars] map file for db '[chars]' in [chars].

Explanation   The specified operation on the map control file for the specified disk database has failed in the named function. See previous event for detailed failure information and next event for error context.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-TBLOPFAIL: Failed to [chars] disk db table '[chars]' in [chars].

Explanation   The specified operation on the specified disk database table has failed in the named function. See previous event for detailed failure information and next event for error context.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-DIRTREERMFAIL: Db '[chars]' directory tree remove failed in [chars].

Explanation   Unable to remove directory tree for the specified database in the named function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-LISTADDFAIL: Db '[chars]' list add to Sync Task failed in [chars].

Explanation   Unable to add specified message to db list for Dbm Sync task to process. See previous event for detailed failure information.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MSGPROCFAIL: Failed to process [chars] msg for db [chars] in [chars].

Explanation   The processing of the specified message for the specified database has failed in the named function. See previous event for detailed failure information.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-SYNCSENDFAIL: Failed to send sync [chars] msg for db [chars] in [chars].

Explanation   The sending of the specified message for the specified database has failed in the named function. See previous event for detailed failure information.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MAPHDRDIFF: Db '[chars]' map file is corrupted. Header field=[chars].

Explanation   The disk map control file in the version directory for the specified database does not contain the correct header information. The database files are corrupt or were restored to the wrong location. The disk or filesystem could also have a problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MAPCSCORRUPT: Db '[chars]' map checksum is corrupted. DiffSum=[hex].

Explanation   The disk flag control file in the version directory for the specified database does not match the correct version. The database files are corrupt or were restored to the wrong location. The disk or filesystem could also have a problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-TBLHDRDIFF: Db Table '[chars]' file is corrupted. Header field=[chars].

Explanation   The disk table file in the version directory for the specified database does not contain the correct header information. The database files are corrupt or were restored to the wrong location. The disk or filesystem could also have a problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-3-TBLELMTCORRUPT: Db Table '[chars]' element [dec] is corrupted. Invalidated.

Explanation   The specified disk table file had a corrupted element. It has been invalidated and reset to the default state. Data has been lost in the table.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-TBLCSCORRUPT: Db '[chars]' map tbl [dec] checksum is corrupted. DiffSum=[hex].

Explanation   The specified database map file for the specified table number does not contain the correct checksum information. The map control file is corrupt or were restored to the wrong location.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-3-TBLDATACHANGED: EVENT_DUMP_TRACE 0 Db Table '[chars]' element [dec] data changed during write.

Explanation   The specified disk table file has been corrupted by data being changed during a write. The commit of the update has been aborted.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MSGINVALID: Received msg [chars] of [dec] is invalid to [chars].

Explanation   The specified field of the message passed as a parameter to the named function was invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MSGTIMEOUT: Db Manager [chars] msg timed-out [dec] secs. Type=[chars].

Explanation   The request to the database manager timed out the response. No response was given in indicated interval. The Database manager could have died or is hung processing this or another request.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-WINDOWTIMEOUT: Db '[chars]' msg window timed-out [dec] secs. Window=[dec].

Explanation   The window resource request to get a buffer window timed out. It was unable to get a resource count in the time specified. Window resources have been lost for the database or message were lost.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MSGNAMEINVALID: Msg [chars] name '[chars]' with key [dec] is invalid to [chars].

Explanation   The specified name in the message passed as parameter to the named function was invalid. It was not found with the hashkey specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MSGSEQUENCEINV: Msg [chars] sequence [dec] is invalid for db '[chars]'. Correct=[dec].

Explanation   The specified sequence number in the message passed as parameter to the named function was invalid. The correct value is specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperrcommand from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-MSGMISMATCH: Msg field [chars] value 0x[hex] is invalid to [chars]. Correct=0x[hex].

Explanation   Internal Messaging Error. The field value for the named parameter passed in as an argument to the named function was invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-2-COMMLOST: Communication for Db '[chars]' has been lost. Retried=[dec].

Explanation   The communication between active and standby has been lost for the specified database name. Communication has been retried the specified number of times. Core Redundancy for the Database has been lost.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-2-SYNCFAIL: Database Sync to standby card failed. Unable to establish Core Redundancy.

Explanation   The syncing of the databases to the standby card failed. Core Redundancy cannot be established.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-6-FILENAME: Db file name=[chars].

Explanation   The specified filename is being reported as part of a file operation or I/O error. This event is associated with that error event from the same task.

Recommended Action   No action required.

Error Message   DBM-4-FILEOPFAIL: EVENT_DUMP_TRACE 0 Db file [chars] failed in [chars]. Fd=[dec] Errno=[hex].

Explanation   The specified operation on a database file failed with the specified error number. There could be a problem with the disk or filesystem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-FILEIOFAIL: EVENT_DUMP_TRACE 0 Db file [chars] failed at [dec]. Fd=[dec] Len=[dec] Errno=[hex].

Explanation   The specified operation on a database file failed with the specified error number. There could be a problem with the disk or filesystem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-DIROPFAIL: EVENT_DUMP_TRACE 0 Db directory [chars] failed. Errno=[hex] Dir=[chars].

Explanation   The specified operation on a database directory failed with the specified error number. There could be a problem with the disk or filesystem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-INTPARMINVALID: Internal parm [chars] value '0x[hex]' is invalid to [chars].

Explanation   Internal API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-INTPARMMAXEXCD: Internal Parm [chars] '[dec]' has exceeded max [dec] to [chars].

Explanation   Internal API Software Error. The parameter value for the named parameter passed in as an argument to the named function exceeded maximum value specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-DBTABLEFULL: Db Table for [chars] is full. All [dec] entries are used.

Explanation   The named table is full. There are no more entries available to create any database ids. The database manager limit needs to be increased.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-4-LISTEMPTY: Db [chars] buffer list is empty when it shouldn't be.

Explanation   The buffer list for the named database is empty when it should not be empty. The process count semaphore indicate there should be a message to process in the list.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   DBM-7-DBCREATE: Creating Disk Database '[chars]' Version [dec].[dec].[dec] on disk.

Explanation   The disk database specified is being created for the first time on disk at the specified version.

Recommended Action   No action required.

Error Message   DBM-7-DBUPGRADE: Upgrading Disk Db '[chars]' from Version [dec].[dec].[dec] to [dec].[dec].[dec].

Explanation   The disk database specified is being upgraded from the specified version to the specified version.

Recommended Action   No action required.

Error Message   DBM-7-DBDOWNGRADE: Downgrading Disk Db '[chars]' to [dec].[dec].[dec]. Changes may be lost!

Explanation   The disk database specified is being downgraded to the specified version.

Recommended Action   No action required.

Error Message   DBM-7-TBLCREATE: Creating Disk Db Table '[chars]' Num Elmts=[dec] Size=[dec] on disk.

Explanation   The disk database table specified is being created for the first time on disk with the specified configuration.

Recommended Action   No action required.

Error Message   DBM-7-SYNCSTART: Starting sync for [chars][chars] on standby card.

Explanation   The syncing of the specified database on the standby card has started. This must complete before the card will go to standby state.

Recommended Action   No action required.

Error Message   DBM-7-SYNCCOMPLETE: Sync complete for [chars][chars] on standby card.

Explanation   The syncing of the specified database on the standby card is complete. This standby card can go to the standby state.

Recommended Action   No action required.

Error Message   DBM-7-PMMACTION: [chars] for [chars][chars].

Explanation   The specified shelf action for the specified database has happened.

Recommended Action   No action required.

File Manager (FILM) Messages

This section contains the File Manager (FILM) messages.

Error Message   FILM-7-SM_FW_DNLD_PASS: [chars]: Firmware Download passed for Slot [dec] Firmware Download passed for Slot [dec]

Explanation   Firmware was downloaded to the Service Module successfully.

Recommended Action   No action required.

Error Message   FILM-7-PXM_FW_DNLD: Downloaded PXM Revision : [chars]

Explanation   This information event indicates that PXM Firmware has been downloaded.

Recommended Action   No action required.

Error Message   FILM-7-PXM_BKUP_DNLD: Downloaded PXM Backup Boot Revision : [chars]

Explanation   PXM Backup Boot Code has been downloaded.

Recommended Action   No action required.

Error Message   FILM-4-BASISTSKSPWNERR: [chars]: Spawn Task Failed TaskName: [chars] Slot No : [dec] File Type : [dec]

Explanation   Unable to create a new task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-4-MSGQ_ERR: QName: [chars] SlotNo: [dec] FileType: [dec] Msg: [chars]

Explanation   Unable to create a message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-4-PARMINVALID: Parm [chars] value '0x[hex]' is invalid to [chars].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-4-DISKWRITEFAIL: EVENT_DUMP_TRACE 0 [chars]: Write to disk failed fileType is [dec]

Explanation   Unable to write file to disk.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-4-MSG2SCMFAIL: EVENT_DUMP_TRACE 0 [chars]: slotNum is [dec] opType is [dec] fileType is [dec]

Explanation   Unable to do intercard communication through SCM.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-4-FW_DNLD_FAILED: Failure Msg: [chars]

Explanation   Firmware download failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-4-FOPEN_FAILED: EVENT_DUMP_TRACE 0 [chars]: slotNum [dec] fileType : [dec] Msg: [chars]

Explanation   Open API of the specified file failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-7-FOPEN_PASSED: [chars]: slotNum: [dec] fileType: [dec] Msg: [chars]

Explanation   Open API of the specified file passed.

Recommended Action   No action required.

Error Message   FILM-4-FREAD_FAILED: EVENT_DUMP_TRACE 0 [chars]: fD: [dec] slotNo: [dec] fileType: [dec] Msg: [chars]

Explanation   File read failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-4-FWRITE_FAILED: EVENT_DUMP_TRACE 0 [chars]: fD: [dec] slotNo: [dec] fileType: [dec] Msg: [chars]

Explanation   File write failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   FILM-7-FCLOSE_EVENT: [chars]: slotNum: [dec] fileType: [dec] Msg: [chars]

Explanation   Closing the specified file.

Recommended Action   No action required.

Error Message   FILM-4-COMPARE_EVT: EVENT_DUMP_TRACE 0 [chars]: Param1 [dec] Param2 [dec] slotNo [dec] fileType [dec] Msg: [chars]

Explanation   Card Type doesn't match the image header.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Hot Standby (HSB) Messages

This section contains messages related to the Hot Standby feature.

Error Message   HSB-4-FUNCFAILSTK: [chars] : HSB subsystem call to [chars] failed. rc=[dec].

Explanation   The specified function call failed. It failed with the specified return code. Astack trace was generated.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-FUNCFAIL: [chars] : HSB subsystem call to [chars] failed. rc=[dec].

Explanation   The specified function call failed. It failed with the specified return code.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-RAMDBINITFAIL: [chars] : Ram DB initialization failed.

Explanation   HSB Ram DB initialization failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Explanation   HSB-4-RAMTBLREGFAIL: [chars] : Ram Table [chars] registration failed.

Explanation   HSB Ram Table registration failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-RAMSTBYUPDFAIL: [chars] : Ram Table 0x[hex] update failed. Elt = [dec].

Explanation   HSB Ram Table update to the standby failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-DBUPDINVACTION: [chars] : Standby update action [dec] invalid.

Explanation   Standby Ram update failed. Invalid action requested.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-DBUPDINVELTS: [chars] : Standby update start elt [dec] num elts [dec].

Explanation   Standby update needs has the wrong number of elements.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-FRMBUFTAKEERR: [chars] : Attempt to get SAR Buffer of len [dec] failed.

Explanation   Attempt to allocate a SAR Frame buffer failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-SSIMSGSENDFAIL: [chars]: ssiMsgSendWaitslot [dec] ptr 0x[hex] len [dec] failed.

Explanation   Sending of incremental update to Hot Standby failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-INCRUPDTFAIL: [chars]: hsbSendMessageToSmslot [dec] ptr 0x[hex] len [dec] failed.

Explanation   Forwarding of incremental update to Hot Standby failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-INCRUPDTDROP: Increment Update from slot [dec] to [dec] mib id row [dec] dropped.

Explanation   Incremental update dropped. Not in Hot Standby state yet.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-DNLDBRAMFAIL: [chars]: downLoadBramfrom [dec] to [dec] failed.

Explanation   Downloading of the configuration to the card failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   HSB-4-BRAMNOTFOUND: [chars]: Could not find configuration file for slot [dec].

Explanation   The configuration for the given slot was not found.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Integrated Local Management Interface (ILMI) Messages

This section contains the Integrated Local Management Interface (ILMI) messages.

Error Message   ILMI-4-INIT_ERROR_ILMI: Init Error: [chars]

Explanation   Unable to create message queues during initialization.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-BAD_SNMP_VER: ILMI_BAD_SNMP_VERSION: [chars]

Explanation   Bad SNMP version.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-ILMI_PARSE_ERR: ILMI_AUTH_PARSE_ERR: [chars]

Explanation   SNMP community string purser error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-5-UNKNOWN_MSG: UNknown message: [chars]

Explanation   Unknown message type received.

Recommended Action   No action required.

Error Message   ILMI-4-SEND_MSG_ERROR: Send Message failed: [chars]

Explanation   Error during sending a message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-RCV_MSG_ERROR: ILMI_RCV_MESSAGE_ERROR : [chars]

Explanation   Error in receiving a message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-INV_COMM_STR: ILMI_INVALID_COMM_STRING: [chars]

Explanation   Invalid ILMI community string.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-ILMI_ASN1_ERR: ILMI_ASN1_PARSE_ERR: [chars]

Explanation   PDU paring function returned error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-INVALID_PDU: ILMI_INVALID_PDU_TYPE: [chars]

Explanation   Received an invalid PDU.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-ILMI_TRAP_ERROR: ILMI_TRAP_ERROR: [chars]

Explanation   Error in ILMI trap.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-MAKE_OCTET_ERR: ILMI_MAKE_OCTET_ERROR: [chars]

Explanation   Error in making octet string.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-MAKE_PDU_ERR: ILMI_MAKE_PDU_ERROR: [chars]

Explanation   Error PDU building function returned error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-MAKE_VARBND_ERR: ILMI_MAKE_VAR_BIND_ERROR: [chars]

Explanation   Error in making Var Bind.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-CLONE_OID_ERR: ILMI_CLONE_OID_ERROR: [chars]

Explanation   Clone Enterprise failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-MAKE_AUTH_ERR: ILMI_MAKE_AUTHENT_ERROR: [chars]

Explanation   Error in authenticating the community string.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-ILMI_SNMP_ERR: ILMI_SNMP_ERROR: [chars]

Explanation   SNMP related error happened.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-INV_PORT_NUM: INVALID_PORT_NUMBER: [chars] port no: [dec]

Explanation   Invalid port number in the parameter sent to this function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-TBL_OVERFLOW: ILMI_PREFIX_TBL_OVERFLOW: [chars]

Explanation   ILMI PrefixTable overflow.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-ILMI_MSG_ERR: ILMI_MSG_ERROR: [chars]

Explanation   Error during sending a message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-BUFALLOC_FAIL: ILMI_TX_BUFF_ALLOC_FAILS: [chars]

Explanation   Memory not available.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-ILMI_OUT_OF_BUF: ILMI_OUT_OF_BUF : [chars]

Explanation   Unable to allocate SAR buffer.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-ILMI_SSI_XMT: ILMI_SSI_XMT_FAILURE : [chars] [dec]

Explanation   Frame transmission function returned error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   ILMI-4-SEM_GET_ERR: SEMAPHORE_GET_ERROR [chars]

Explanation   Error while taking a semaphore.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Installation Module (INST) Messages

This section contains the Installation Module (INST) messages.

Error Message   INST-4-INSTALL_ERROR: Init Error: [chars]

Explanation   Initialization error in upgrade task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-WRNG_EVT_RCVD: [chars] CurrentEvent = [dec]

Explanation   Wrong event received.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-GET_MSG_ERROR: Get Message: [chars]

Explanation   Error in receiving messages.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-GET_BUFF_ERROR: Get pipcGetBuffer Error: [chars]

Explanation   Error in allocating a buffer.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-GET_EVENT_ERROR: Get Event: [chars] [dec]

Explanation   Bad event received.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-5-UNKNOWN_MSG: UNknown message: [chars]

Explanation   Unknown message type received.

Recommended Action   No action required.

Error Message   INST-4-SEND_MSG_ERROR: Send Message failed: [chars]

Explanation   Error in sending a message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-RCV_MSG_FAILED: Init Error: [chars]

Explanation   Error in receiving a message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-5-INVALID_SLOT_NO: Invalid Slot Number [chars] [dec]

Explanation   This function received an invalid input parameter.

Recommended Action   No action required.

Error Message   INST-7-SLOT_NO_SET: updateSlotNum: Old S.N.= [dec] New S.N.=[dec]

Explanation   Successful slot number update.

Recommended Action   No action required.

Error Message   INST-7-GOT_SYNC_MSG: Got Sync Msg from INSTALL Msg Q Id = [dec]

Explanation   Received a sync message from INSTALL.

Recommended Action   No action required.

Error Message   INST-7-TIMER_EXPIRED: Timer Expired = [chars]

Explanation   Timer expired notification.

Recommended Action   No action required.

Error Message   INST-7-ACCESS_FILE_ERR: [chars] : File Access Error for Upgrade/Downgrade

Explanation   File read or write error.

Recommended Action   No action required.

Error Message   INST-4-MSGTO: [chars] : timeout waiting for response

Explanation   Timeout waiting for response.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-MSGNAK: [chars] : negative ack received

Explanation   NAK message received notification.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-INVMSG: [chars] : invalid message type [dec]

Explanation   Invalid card message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-RCVERR: [chars] : error returned by ssiMsgReceive [dec]

Explanation   Error in receiving a CLI message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-4-SENDERR: [chars] : error returned by ssiMsgSend [dec]

Explanation   Error in sending a CLI message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-7-RESET: EVENT_WRITE_BRAM EVENT_NO_ACTION [chars]

Explanation   Other PXM has successfully been reset.

Recommended Action   No action required.

Error Message   INST-7-ABORT: [chars] : aborting process current state [dec]

Explanation   Starting the abort of all processes.

Recommended Action   No action required.

Error Message   INST-4-COPYERR: [chars] : error copying [chars] to other PXM [dec]

Explanation   Downloading FW to a card failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   INST-7-COPY: [chars] : copying [chars] to other PXM

Explanation   Downloading Firmware notification.

Recommended Action   No action required.

Error Message   INST-7-COPYDONE: [chars] : copying [chars] to other PXM done

Explanation   Downloading of Firmware is successful.

Recommended Action   No action required.

Error Message   INST-7-CHANGESTATE: [chars] : changing state from [dec] to [dec]

Explanation   Change of state notification.

Recommended Action   No action required.

Error Message   INST-7-CHANGESTATETO: [chars] : changing state to [dec]

Explanation   Change of state notification.

Recommended Action   No action required.

Error Message   INST-7-COMMAND0: [chars]

Explanation   rstupgrade command notification.

Recommended Action   No action required.

Error Message   INST-7-COMMAND1: [chars] [chars]

Explanation   Beginning of install.

Recommended Action   No action required.

Error Message   INST-7-COMMAND2: [chars] [chars] [chars]

Explanation   Notification of setting primary/secondary PXM image.

Recommended Action   No action required.

Error Message   INST-7-COMMAND3: [chars] [chars] [chars] [chars]

Explanation   install command notification.

Recommended Action   No action required.

Line Driver (LDRV) Messages

This section contains the Line Driver (LDRV) messages.

Error Message   LDRV-4-DBNUMLINEINVLD: Function= [chars]: Line number [dec]..[dec] exceeded Max [dec] Line per PSM.

Explanation   Config update function detected number of requested lines exceed the maximum number of line in the PSM.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-DBVERSIONINVLD: Invalid Database version detected: for [chars] from:[dec].[dec] to:[dec].[dec]

Explanation   Unable to update the configuration data base because of the invalid DB version number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-PORTNUMINVLD: [chars]:Invalid Port number: [dec]

Explanation   Requested function detected invalid Port number passed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-UNKNOWNDCTYPE: In function [chars] Unknown Daughter card type [dec] is detected

Explanation   The pio does not indicate a known daughter card type.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-RCMPCONINVLD: Invalid RCMP connection size: [dec] for the DC card = [chars]

Explanation   The DC identification bits are invalid for number of RCMP connection.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-FPGADNLDERR: Fpga download on card ID = [dec] failed

Explanation   System routine to download FPGA image on a card returns fail.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-BCDCMISMATCH: Back Card and Daughter card types don't match BC=[dec] DC=[dec]

Explanation   Back card and daughter card type are mismatched.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-LINEALARMCHG: Line Alarm on port = [dec] severity = [chars]

Explanation   Line alarm has been switched to a new state. The severity can be Major, Minor or Clear.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-LINESTATALARM: Statistical Alarm on Port: [dec] severity =[chars]

Explanation   Statistical alarm has been switched to a new state. The severity can be Major, Minor or Clear.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-PLCPALARM: Plcp Alarm on Port: [dec] severity =[chars]

Explanation   Plcp alarm has been switched to a new state. The severity can be Major, Minor or Clear.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-PLCPSTATALARM: Plcp Statistical Alarm on Port: [dec] severity =[chars]

Explanation   Plcp alarm has been switched to a new state. The severity can be Major, Minor or Clear.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-7-CARDTYPEACTION: [chars] of type [chars] [chars]

Explanation   Back card or Daughter card inserted or removed Line Driver enters Fail state if BC or DC is removed Line Driver enters Standby state if both BC and DC are inserted and matched.

Recommended Action   No action required.

Error Message   LDRV-4-UNKNOWNBCTYPE: Unknown Backcard card [dec]

Explanation   The NOVRAM read from the card does not have a valid backcard type. The Line Driver enters Fail state until a valid back card is inserted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-RCMPRSTFAIL: RCMP reset Failed for DC type [chars]

Explanation   RCMP reset fail for the specified Daughter card. Line Driver enters Fail state.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-5-MSGLENGTHINVLD: Invalid Message length = [dec]

Explanation   Invalid CMM Message length on this receive queue. Line Driver discarded the message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-5-CARDSTATEINVLD: Invalid card state set request [dec]

Explanation   CMM requests to set an invalid card state. Line Driver discarded the message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-5-APPLTYPEINVLD: Invalid Message request type [dec]

Explanation   CMM requests an invalid message type. Line Driver discarded the message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-5-MSGSRCIDINVLD: Message from an unexpected source [dec]

Explanation   Message from an unexpected source. Line Driver discarded the message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-5-MISDIRECTEDMSG: Misdirected message [dec]

Explanation   Message not intended for Ldrv is detected. Line Driver discarded the message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-RCVMSGFAILED: Unable to receive message in the message queue

Explanation   SSI receive message routine detected an error. Message is being lost.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-MIBCNFMISMATCH: HW card types don't match MIB cfg HW=[chars] MIB= [chars]

Explanation   DC and C type did not match with the MIB config type This could happen when user is swapping different line cards. Line Driver will use default configuration.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-SONETLINEINVLD: Invalid sonetLine/sonetCfg Number [dec] in Config data base. Expected lineNum= [dec]

Explanation   Sonet Line number does not match with the configuration database.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-SCRAMOPTINVLD: Invalid frameScrambling option = [dec] in Config data base

Explanation   Invalid SONET Scrambling option is detected in the configuration. It has to be either enabled or disabled. Line Driver will reset config to default value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-SONETMEDINVLD: Invalid sonet medium [dec] in BRAM is detected

Explanation   Invalid SONET medium is detected in the configuration. Line Driver will reset config to default value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-SECTRACEINVLD: Invalid section Trace Number [dec] in Config data base is detected

Explanation   Invalid section Trace Number is detected in the configuration. Line Driver will reset config to default value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-ALMSERVINVLD: Invalid statSeverity/lineAlmCfg [dec] in Config data base is detected

Explanation   Invalid statSeverity/lineAlmCfg is detected in the configuration. Line Driver will reset config to default value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-DS3LNINVLD: Out of Range 1..255 dsx3LineLength= [dec] in Config data base is detected

Explanation   dsx3LineLength not in the range of 1..255. Line Driver will reset config to default value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-DS3REDSERV: Out of Range minor..major dsx3RedSeverity= [dec] in Config data base is detected

Explanation   dsx3RedSeverity is not in the range of detected minor..major. Line Driver will reset config to default value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-DS3LINEINVLD: Invalid line number = [dec] in Config data base is detected. Expected LineNum=[dec]

Explanation   dsx3LineLength not in the range of 1..255. Line Driver will reset config to default value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-DBREGISTERERR: Fail to registering [chars] data base type = [dec] version= [chars]

Explanation   Unable to register the Line Driver data base. Ldrv task will not be able to spawn properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-DBTBLERROR: Fail to register TBL [chars] NumElm=[dec] ElmSize=[dec] Upgrd=0x[dec]wngrd=0x

Explanation   Unable to register a table entry into the database. Ldrv task will not be able to spawn properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-DBTBLIDINVLD: [chars] Table [chars]: is invalid. Table type=[dec] Line Number=[dec]

Explanation   Unable to read/update database entry because of invalid table ID. Ldrv task will not be able to spawn properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-DBMISMATCH: Database does not matched with the line type =[dec]. Default the configuration

Explanation   The database has information that conflicts with the current Back card type. Line Driver will reset config to default value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-PLPPDS3LNINVLD: In Function [chars] Line number [dec] is invalid Not in range of 1..2

Explanation   Unable to read/write DSx3 PLPP register because of invalid line number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-PLPPOC3LNINVLD: In Function [chars] Line number [dec] is invalid Not in range of 1..2

Explanation   Unable to read/write OC3 PLPP register because of invalid line number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-PLPPOC12LNINVLD: In Function [chars] Line number [dec] is invalid Not in range of 1..2

Explanation   Unable to read/write OC12 PLPP register because of invalid line number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-CLKIMPINVLD: External Clock impedance = [dec] is invalid

Explanation   External Clock impedance is invalid. Expected value is 75 or 120 Ohms.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-CLKCONNINVLD: External Clock connector type = [dec] is invalid

Explanation   External Clock connector type is invalid. Expected value is RJ45 or SMB.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-CLKINBAND1INVLD: Inband recovered Clock line number = [dec] is invalid

Explanation   Inband recovered clock has invalid line number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-CLKINBAND2INVLD: Inband Frame Pulse Clock has line number = [dec] is invalid

Explanation   Inband Frame Pulse Clock has invalid line number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-CLKOPTINVLD: Requested Inband Frame Pulse Clock source = [dec] but configuration doesn't allow it

Explanation   Requested Inband Frame Pulse Clock source but configuration doesn't allow it.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-CLKSRCUNKNOWN: Unable to config requested clock source because clock source [dec] is unknown

Explanation   Unable to config requested clock source because clock source is unknown.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-CLKMUXUNKNOWN: Unable to config requested clock source because clock MUX [dec] is unknown

Explanation   Unable to config requested clock source because clock MUX is unknown.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-4-CLKSRCCHANGE: Current Clock source changed to [chars]

Explanation   Line Driver Clock source changed the current clock source selection.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-7-CLKSETREQ: Clock config Set for [chars] clock source

Explanation   An SNMP config set request is made to the clock module to switch clock.

Recommended Action   No action required.

Error Message   LDRV-7-SETIFERR: Set Interface Type for Port = [dec] with invalid type [dec]

Explanation   A request was made to set interface type with invalid ifType.

Recommended Action   No action required.

Error Message   LDRV-4-INVALID_PARMS: QUNI: Invalid Parameters: [chars] [dec]

Explanation   Invalid parameters passed into function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   LDRV-6-QUNI_CFG_COND: QUNI chip Cfg for all lines MIB_OBJ: [chars][dec]

Explanation   Some of QUNI chip config parameters apply to all lines, even when a change is effected through one MIB object

Recommended Action   No action required.

Operations Administration and Management Module (OAM) Messages

This section contains the Operations Administration and Management Module (OAM) messages.

Error Message   OAM-7-INIT_SUCCESS: OAM : Task Init Success

Explanation   OAM Task Init Success.

Recommended Action   No action required.

Error Message   OAM-7-RCV_MSG_FAIL: OAM : Message Receive Failed

Explanation   Message receive failed.

Recommended Action   No action required.

Error Message   OAM-7-RCV_CELL_FAIL: OAM : Cell Receive from SAR Failed

Explanation   Failure in receiving a cell.

Recommended Action   No action required.

MGX Inter Process Communication (PIPC) Messages

This section contains the MGX Inter Process Communication (PIPC) messages.

Error Message   PIPC-4-MAJ_ERR_LOG: [chars]

Explanation   PIPC Severe Error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

MGX Management Module (PMM) Messages

This section contains the MGX Management Module (PMM) messages.

Error Message   PMM-4-SWITCH_DEFAULT: Switch default: [chars] [dec]

Explanation   The 'default' case in a switch statement has been hit.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-SWCH_DEF_STR: Switch default: [chars] [dec]

Explanation   The 'default' case in a switch statement has been hit.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-SYNC_REQ_ERR: Sync request to [chars] with slot [dec] failed

Explanation   Synchronization request between requested slots failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-BUF_ERR: Get Buffer failed: [chars] [dec]

Explanation   Buffer allocation failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-MSG_RSP_ERR: MSG resp err: [chars] [dec]

Explanation   Message error happened during sending a response.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-MSG_Q_ERR: MSG Q Err: [chars] [dec]

Explanation   Error happened in sending a message.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-5-PMM_TOUT: PMM Timeout: [chars] [dec]

Explanation   PMM time out.

Recommended Action   No action required.

Error Message   PMM-5-TMR_ERR: TimerError: [chars] [dec]

Explanation   Application Timer Add function failed.

Recommended Action   No action required.

Error Message   PMM-7-SWITCHOVER: Switchover: [chars] [dec]

Explanation   Card assuming Mastership.

Recommended Action   No action required.

Error Message   PMM-7-IF_ERR: Interface Error: [chars] [dec]

Explanation   Input parameter to a function is invalid or a task reported error.

Recommended Action   No action required.

Error Message   PMM-4-API_ERR: [chars]: External API [chars] returns Error\n

Explanation   API Error. This error occurs when an API of a different module, such as SSI, returns an error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-5-TASK_SPAWN_ERR: [chars]: ssiTaskSpawn\[chars]\ [chars]: 0x

Explanation   Unable to create a new task.

Recommended Action   No action required.

Error Message   PMM-7-INIT_ERR: INIT Error: [chars]

Explanation   Initialization error.

Recommended Action   No action required.

Error Message   PMM-4-FSM_ERR: FSM Error: [chars] cur=[chars] prev=[chars] evt=[chars]

Explanation   Invalid state or received invalid event as an input parameter.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-7-FSM_RPT: FSM Report: [chars] cur=[chars] evt=[chars]

Explanation   A peer communication between the Master and the slave happened.

Recommended Action   No action required.

Error Message   PMM-4-GO_ACTIVE_ERR: Go Active sync failed in module [chars]

Explanation   Error occurred while trying to go active.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-7-RST_REQ: Reset request: [chars] [dec]

Explanation   Resetting either Master or the Slave.

Recommended Action   No action required.

Error Message   PMM-4-DB_ERR: Database Error: [chars] [dec]

Explanation   Database update failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-DNLD_ERR: Standby Update Error: [chars]

Explanation   Download or RAM update error occurred.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-RED_STATUS: Redundancy Status Change for bit [chars] now [chars]

Explanation   Redundancy status changed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-7-BCAST_DATETIME: Periodic Broadcast of Date and Time to SMs and Standby PXM

Explanation   This information event indicates that the date and time is broadcast periodically to SMs and Standby PXM.

Recommended Action   No action required.

Error Message   PMM-7-ENET_ENABLE: [chars]: Enabling Ethernet Interface on ActivePXM in Slot [dec]

Explanation   This information event indicates that the Ethernet interface on Active PXM is enabled.

Recommended Action   No action required.

Error Message   PMM-7-CLR_DB_REQ: [chars]: Clearing the Database due to new FW download and reset request from Master PXM

Explanation   This information event indicates that the Database is to be cleared on the Standby, whenever a new fw is downloaded and reset request from Master PXM is issued.

Recommended Action   No action required.

Error Message   PMM-7-NNAME_RCVD: [chars]: Nodename is [chars] Nodename Trap received by Platform PMM

Explanation   This information event indicates that the nodename from VSI Controllers (PAR) is received by the platform.

Recommended Action   No action required.

Error Message   PMM-4-ADC_CONV_ERROR: ADC Conversion Failed

Explanation   ADC Conversion error happened.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-ADC_ERROR: ADC Error

Explanation   ADC related error happened.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-4-ADC_MIDCAL_ERR: ADC MidVoltage calculation error

Explanation   ADC MidVoltage calculation error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   PMM-7-ASM_READING: ASM Reading : [chars]

Explanation   Successfully Read Fan RPM.

Recommended Action   No action required.

Queue Engine (QE) Messages

This section contains the Queue Engine (QE) messages.

Error Message   QE-4-FAIL2REFRESH: QE Initialization Error: qeInitConfigReg

Explanation   The specified QE is unable to initialize during the refresh cycle.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   QE-4-EXPMANTISAFAIL: QE Initialization Error: qeSetAcpCellCntRam

Explanation   The specified QE is unable to convert Cell Loss Threshold into Exp format.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   QE-4-UNKNOWNINT: QE Unknown Interrupt Error: EQ No: [dec] status1 = [dec] status2 = [dec] status3 = [dec]\n

Explanation   The specified QE got unknown interrupt signal from the system.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   QE-4-ERRINTERRUPT: QE Unknown Interrupt Error: QE No: [dec] status1 = [dec] status2 = [dec] status3 = [dec]\n

Explanation   The specified QE got error interrupt signal from the system.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Routing, Control, Monitoring, and Policing (RCMP) Messages

This section contains the Routing, Control, Monitoring, and Policing (RCMP) messages.

Error Message   RCMP-4-INIT_ERR: rpDriverInit: Error exit due to [chars]

Explanation   rpDriverInit routine failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RCMP-7-GEN_ERR: [chars]

Explanation   General Error.

Recommended Action   No action required.

Error Message   RCMP-7-ADD_CON_ERR: [chars] [dec]

Explanation   Error while adding connections.

Recommended Action   No action required.

Error Message   RCMP-7-SRAM_ERR: [chars]

Explanation   Static RAM read/write error occurred.

Recommended Action   No action required.

Redundancy Module (RED) Messages

This section contains the Redundancy Module (RED) messages.

Error Message   RED-7-MSGQSEND: ACRED: Could not send MSG to SM

Explanation   AC_SEND_MSG_FAILED_ERR

Recommended Action   No action required.

Error Message   RED-7-GENERAL: ACRED: General ERROR

Explanation   AC_GEN_ERR

Recommended Action   No action required.

Error Message   RED-7-INFORM: ACRED: Informational

Explanation   AC_INFO_ERR)

Recommended Action   No action required.

Error Message   RED-7-MEMCORRT: ACRED: Memory corruption in system

Explanation   AC_MEM_ERR

Recommended Action   No action required.

Error Message   RED-7-TIMEOUT: ACRED: State Time out

Explanation   AC_TIME_OUT_ERR

Recommended Action   No action required.

Error Message   RED-7-WRONGMSG: ACRED: Wrong Message Received

Explanation   AC_WRONG_MSG_ERR

Recommended Action   No action required.

Error Message   RED-7-DNLDERR: ACRED: Download BRAM Failed

Explanation   AC_DWNL_BRAM_ERR

Recommended Action   No action required.

Error Message   RED-7-UPLDERR: ACRED: Upload BRAM Failed

Explanation   AC_UPLD_BRAM_ERR

Recommended Action   No action required.

Error Message   RED-7-MSG_DATA_ERROR: msg data err [chars]

Explanation   Message error. Data Errors and Unknown Msgs.

Recommended Action   No action required.

Error Message   RED-7-AC_SEND_MSG_ERR: Could not send MSG to SM [chars]

Explanation   Auto Card send message failed error.

Recommended Action   No action required.

Error Message   RED-7-AC_GEN_ERR: General ERROR [chars]

Explanation   Auto Card PMM related failure / BRAM related failure.

Recommended Action   No action required.

Error Message   RED-7-AC_INFO_ERR: Error Event [chars]

Explanation   Autocard error event.

Recommended Action   No action required.

Error Message   RED-7-AC_MEM_ERR: Memory error in system [chars]

Explanation   Auto Card memory error.

Recommended Action   No action required.

Error Message   RED-7-AC_TIME_OUT_ERR: State Time out [chars]

Explanation   Auto Card time out error.

Recommended Action   No action required.

Error Message   RED-7-AC_WRNGMSG_ERR: ACRED: Wrong msg rcvd [chars]

Explanation   Auto Card wrong message type error.

Recommended Action   No action required.

Error Message   RED-7-AC_DWNLBRAMERR: ACRED: Download BRAM Failed [chars]

Explanation   BRAM download error.

Recommended Action   No action required.

Error Message   RED-7-AC_UPLDBRAMERR: ACRED: Upload BRAM Failed [chars]

Explanation   BRAM upload error.

Recommended Action   No action required.

Error Message   RED-7-BADARCERR: [chars]: BAD Archive from slot [dec].

Explanation   Service Module received a bad configuration file.

Recommended Action   No action required.

Error Message   RED-7-SMM_ERROR_GEN: General Error [chars]

Explanation   General system error.

Recommended Action   No action required.

Error Message   RED-7-SMM_INFO: System Information : [chars]

Explanation   System Information.

Recommended Action   No action required.

Error Message   RED-7-BAD_SHLF_SLOT: Bad shelf slot num [chars]

Explanation   SMM bad shelf slot.

Recommended Action   No action required.

Remote File System (RFS) Messages

This section contains the Remote File System (RFS) messages.

Error Message   RFS-4-NO_IPC_BUFFER: [chars]:[dec]: Could not get IPC buffer.

Explanation   Unable to get buffer for communication.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RFS-4-PORT_CREATE_ERR: Could not create port: [chars].

Explanation   Unable to create port for communication.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RFS-4-TASK_SPAWN_ERR: Could not spawn task [chars].

Explanation   Unable to spawn task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RFS-4-UNKNOWN_MSG: Unknown message received at [chars]. Type: [dec].

Explanation   Unknown message received.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RFS-4-UNSUPPORTED_MSG: Unsupported message received at [chars]. Type: [dec].

Explanation   Unsupported message received.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RFS-4-REQ_DROP: RFS request type [dec] DROPPED.

Explanation   RFS request dropped.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

RPM Management Module (RMM) Messages

This section contains the RPM Management Module (RMM) messages.

Error Message   RMM-4-NO_IPC_BUFFER: [chars]:[dec]: Could not get IPC buffer.

Explanation   Unable to get buffer for communication.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-PORT_CREATE_ERR: Could not create port: [chars].

Explanation   Unable to create port for communication.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-SEAT_CREATE_ERR: Could not create seat: [chars].

Explanation   Unable to create seat for communication.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-SEAT_DELETE_ERR: Could not delete seat: [chars].

Explanation   Unable to delete seat.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-TASK_SPAWN_ERR: Could not spawn task [chars].

Explanation   Unable to spawn task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-UNKNOWN_MSG: Unknown message received at [chars]. Type: [dec].

Explanation   Unknown message received.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-INIT_ACK_ERR: Could not ACK init of task [chars].

Explanation   Unable to ack task init.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-TASK_INIT_ERR: Task initialization failed for [chars].

Explanation   Unable to init task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-TSK_GO_ACT_ERR: Task [chars] could not go ACTIVE.

Explanation   Task unable to go ACTIVE.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-CRDRDY_WAIT_ERR: Wait for card ready failed for [chars].

Explanation   Unable to wait for card ready in task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-CRDACT_WAIT_ERR: Wait for card ACTIVE failed for [chars].

Explanation   Unable to wait for the card to go ACTIVE.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-UNREACHABLE: Unreachability violation in [chars]:[dec].

Explanation   Unexpected seat transport_type.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-7-RESYNC_SUCCESS: RMM seat resync success!!

Explanation   RMM seat resync success!!

Recommended Action   No action required.

Error Message   RMM-4-SEAT_RESYNC_ERR: RMM seat resync failed.

Explanation   Unable to resync seats.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-SEAT_NOT_UP: Seat not up to [chars].

Explanation   Seat is not up.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-INIT_FAILURE: Initialization failure : [chars].

Explanation   Initialization failure : check string for details.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-BAD_NUM_VALUE: [chars][dec]

Explanation   Unexpected numeric value or return code.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RMM-4-BAD_STR_VALUE: [chars][chars]

Explanation   Unexpected string value or return code.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

RPM Virtual Task (RVT) Messages

This section contains the RPM Virtual Task (RVT) messages.

Error Message   RVT-4-INIT_ERROR: Init Error : [chars]

Explanation   Error occurred when RVT task tried to initialize.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RVT-4-IOS_ERROR: IOS IPC Error : [chars]

Explanation   An IOS IPC error occurred.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RVT-4-BULK_SUBIF_ERR: RPM Bulk Update failed for slot [dec]

Explanation   RPM sub interface bulk update failed. There will be inconsistency between the database in RPM and PXM.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   RVT-4-CONN_RESYNC_ERR: Conn Resync Error : [chars]

Explanation   A conn resync error occurred.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Segmentation and Reassembly (SAR) Messages

This section contains the Segmentation and Reassembly (SAR) messages.

Error Message   SAR-4-SAR_DMA_ERR: SAR DMA Error : [chars] qe_no [dec] error-id [dec] error-loc [dec]

Explanation   DMA error has happened.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Shelf Communication Module (SCM) Messages

This section contains the Shelf Communication Module (SCM) messages.

Error Message   SCM-7-MSGQRCV: <[chars]> rcv msg error:

Explanation   Error in receiving message.

Recommended Action   No action required.

Error Message   SCM-4-SPI_ERROR: [chars] [dec]

Explanation   SPI path addition failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-INIT: psmScmInit failed

Explanation   SCM initialization failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-UNKNOWN_MSG: unknown msg[chars] msgQid 0x[hex] srcId [dec] msgFmt [dec] msgType 0x[hex]

Explanation   Unknown message type received.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-SEND_FAIL: [chars] msgType 0x[hex] msgQid 0x[hex] msgLen [dec]

Explanation   SCM SSI message send to application failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-OVERSIZE_FRAME: Over size frame [dec]

Explanation   Frame bigger than the expected size received.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-UNKNOWN_VALUE: <[chars]> unknown [chars] [dec]

Explanation   Unknown cardInx value.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-UNKNOWN_FRAME: unknown frame msgQid [dec] [chars] [dec]

Explanation   Unknown frame received.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-WRONG_STATE: Wrong state: [chars]: slot [dec]: state [dec]

Explanation   Card is in the wrong state.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-NULLPTR: <[chars]> Data pointer is NULL

Explanation   NULL pointer encountered.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-SCM_Q_OVERFLOW: slot [dec] priority [dec]

Explanation   SCM queue overflow.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-SCM_PRI_ERROR: slot [dec] priority [dec]

Explanation   Retransmit queue is empty.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-NODEST: Card [dec] doesn't exist [dec] [dec]

Explanation   Destination not present.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-SEQ_NUM_MISMTCH: Mismatched sequence number for slot[dec]: expected [dec] rcv [dec]

Explanation   SCM frame sequence number mismatch.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-OUT_OF_BUF: [char] Out of buffer

Explanation   SSI frame buffer allocation function returned error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-SAR_RCV: Sar Rcv error rxStatus [dec]

Explanation   Error in receiving SAR buffer.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-SSI_XMT: ssiFrameXmt failed, error status [dec]

Explanation   Frame transmission error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-4-RESP_TIMEOUT: Timeout waiting for response for slot [dec] report to PMM

Explanation   Response time out.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SCM-7-DEBUG: &msgEventScmDebug[0]

Explanation   Debug event.

Recommended Action   No action required.

Selftest Module (SLFT) Messages

This section contains the Selftest Module (SLFT) messages.

Error Message   SLFT-4-SLFTST_FAILED: Card Fails due to Selftest Failure

Explanation   Selftest of the card failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Simple Network Management Protocol (SNMP) Messages

This section contains the Simple Network Management Protocol (SNMP) messages.

Error Message   SNMP-4-INVALIDINPUT: One of the inputs to the function [chars] was invalid.

Explanation   API Software Error. The parameter value for one of the parameters passed in as an argument to the named function was invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-PARMINVALID: Parm [chars] value '0x[hex]' is invalid to [chars].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-PARMINVLENGTH: Parm [chars] invalid length of [dec] to [chars]. Max=[dec] Value='[chars]'

Explanation   API Software Error. The named parameter passed in as an argument to the named function either had a length of zero or exceeded the maximum value specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-FUNCFAILSTK: [chars] : SNMP subsystem call to [chars] failed. rc=[dec].

Explanation   The specified function call failed. It failed with the specified return code. A stack trace was generated.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-FUNCFAIL: [chars] : SNMP subsystem call to [chars] failed. rc=[dec].

Explanation   The specified function call failed. It failed with the specified return code.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-PARMOUTOFRANGE: [chars] : Parm [chars] '[dec]' is out of range [dec]-[dec].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function is out of the specified range of values.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-MALLOCFAILED: [chars] : Call to ssiMalloc failed.

Explanation   A call to allocate more memory has failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-OPENTRANSFAIL: OpenTransport failed.

Explanation   An attempt to open the IP layer transport failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-BINDTRANSFAIL: BindTransport failed.

Explanation   An attempt to bind to the IP layer transport failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-RCVFRTRNSFAIL: ReceiveFromTransport failed.

Explanation   An attempt to receive a message from the IP layer failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-MSGSENDFAIL: [chars]: cntpMsgSendQueue [chars] ptr 0x[hex] len=[dec] failed.

Explanation   An attempt to send a control point message failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-MSGRECVFAIL: [chars]: cntpMsgRecvQueue [chars] failed.

Explanation   An attempt to receive a control point message buffer failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-BADSRMSLOT: [chars]: Invalid SRM slot [dec].

Explanation   Invocation of a function using an invalid SRM slot.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-BADCARDTYPE: Could not send trap [dec] from slot [dec] sequence num [dec].

Explanation   An attempt to generate a trap resulted in an error. The card type of the originating slot could not be identified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-INVVARBIND: [chars] : Invalid Varbind type [dec].

Explanation   An invalid varbind was detected during processing.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-SEMCREATEERR: [chars] : cntpSemBCreate failed.

Explanation   An attempt to create the control point semaphore failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-SEMTAKEERR: [chars] : cntpSemBTakeBasisTrapSem 0x[hex] failed.

Explanation   An attempt to take the control point semaphore failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-SEMGIVEERR: [chars] : cntpSemBGiveBasisTrapSem 0x[hex] failed.

Explanation   An attempt to give the control point semaphore failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-BUFTAKEERR: [chars] : cntpMsgBufTakedataLn=[dec] failed.

Explanation   An attempt to take a control point message buffer failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-FRMBUFTAKEERR: [chars] : Attempt to get SAR Buffer of len [dec] failed.

Explanation   An attempt to allocate a SAR Frame buffer failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-7-TOOFEWVARBINDS: Trap [dec] from slot [dec] has only [dec] of the mandated Robust Trap varbinds.

Explanation   An attempted trap generation was disallowed.

Recommended Action   No action required.

Error Message   SNMP-7-NOTRAPS: [chars] : Trap dropped because they are disallowed.

Explanation   An attempted trap generation was disallowed.

Recommended Action   No action required.

Error Message   SNMP-6-TRAPLOG_WRAP: SNMP : Trap log wrapped around.

Explanation   The RTM trap log buffer has wrapped around.

Recommended Action   No action required.

Error Message   SNMP-6-RPMPORTCLOSED: Port for RPM slot=[dec] already closed.

Explanation   An attempt to close an RPM port failed because the port was already closed

Recommended Action   No action required.

Error Message   SNMP-4-RPMOPENPORT: Opening RPM Port [chars] for slot=[dec] failed.

Explanation   An attempt to open an RPM port failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-OPENPORT: [chars] : Opening Port [chars] failed.

Explanation   An attempt to open an IPC port failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-PROCESSDEQ: [chars] : Call to process_dequeue0x[hex] failed.

Explanation   A call to process_dequeue() failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-CREATEWATCHEDQ: [chars] : Call to create_watched_queue[chars] failed.

Explanation   A call to create_watched_queue() failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-CREATENAMEDPORT: [chars] : Call to ipc_create_named_port[chars] failed.

Explanation   A call to ipc_create_named_port() failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-GETPAKMSGFAIL: [chars] : Call to ipc_get_pak_message failed.

Explanation   A call to ipc_get_pak_message() has failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-IPCSENDMSGFAIL: [chars] : Call to ipc_send_message failed.

Explanation   A call to ipc_send_message() has failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-MSG_TOO_SMALL: [chars] : Message of len [dec] was rejected as too small.

Explanation   A message of a given length was considered too small.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-SOIINITFAIL: [chars] : Could not spawn PXM SOI Task.

Explanation   A message of a given length was considered too small.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-DISKDBINITFAIL: [chars] : Disk DB initialization failed.

Explanation   SNMP Disk DB initialization failed.

Recommended Action   opy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-DISKTBLREGFAIL: [chars] : Disk Table [chars] registration

failed.

Explanation   SNMP Disk Table registration failed.

Recommended Action   opy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-RAMDBINITFAIL: [chars] : Ram DB initialization failed.

Explanation   SNMP RAM DB initialization failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-RAMTBLREGFAIL: [chars] : Ram Table [chars] registration failed.

Explanation   SNMP RAM Table registration failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-RAMSTBYUPDFAIL: [chars] : Ram Table 0x[hex] update failed. Elt = [dec].

Explanation   SNMP RAM Table update to the standby failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-DBUPDINVACTION: [chars] : Standby update action [dec] invalid.

Explanation   Standby RAM update failed. Invalid action requested.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-DBUPDINVELTS: [chars] : Standby update start elt [dec] num elts [dec].

Explanation   Standby update has the wrong number of elements.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   Error Message SNMP-4-DISKDBREADFAIL: [chars] : Disk DB Read failed.

Explanation   Explanation SNMP Disk DB Read failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-DISKDBUPDTFAIL: [chars] : Disk DB Update for elt [dec]

failed. Status [dec].

Explanation   SNMP Disk DB Update failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-5-MSG_DROPPED: SNMP request from [dec].[dec].[dec].[dec] dropped due to lack of buffers.

Explanation   An SNMP request was dropped due to inadequate resources.

Recommended Action   No action required.

Error Message   SNMP-5-TRAP_DROPPED: Could not generate SNMP trap due to lack of buffers.

Explanation   An SNMP trap was dropped due to inadequate resources.

Recommended Action   No action required.

Error Message   SNMP-5-TRAPBADSTATE: Could not generate SNMP trap because the PXM state was invalid.

Explanation   An SNMP trap was dropped because PXM state was invalid.

Recommended Action   No action required.

Error Message   SNMP-5-NONRTMTRAP: Non-RTM SNMP trap generic trap = [dec] specific trap = [dec] disallowed.

Explanation   An attempt to generate a non-RTM SNMP trap was rejected.

Recommended Action   No action required.

Error Message   SNMP-4-UNKNOWNMSG: Unknown message received by [chars] from source [dec]

Explanation   A message was received from an unexpected source.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SNMP-4-CLONETRAPERR: [chars]

Explanation   API Error. Error in cloning an SNMP trap.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Switch Path Interface (SPI) Messages

This section contains the Switch Path Interface (SPI) messages.

Error Message   SPI-4-SDRV_PATH_ERR: Switch Driver Error : [chars] glcn [dec] error-id [dec] error-loc [dec]

Explanation   Switch Path related error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SPI-4-SDRV_CD_ERR: Switch Driver Error : [chars] error-id [dec] error-loc [dec]

Explanation   Card driver error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SPI-4-SDRV_VI_ERR: Switch Driver Error : [chars] vi [dec] error-id [dec] error-loc [dec]

Explanation   VI related error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SPI-4-SDRV_QB_ERR: Switch Driver Error : [chars] qbin [dec] error-id [dec] error-loc [dec]

Explanation   QB error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SPI-4-SDRV_ERR: Switch Driver Error : error-id [dec]

Explanation   SDRV error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Switch Path Management (SPM) Messages

This section contains the Switch Path Management (SPM) messages.

Error Message   SPM-7-SHELFDB_INIT: Shelf Archive file header init failed [chars]

Explanation   Failed to initialize shelf archive file header.

Recommended Action   No action required.

Error Message   SPM-7-SPM_SMDB_INIT: Slot [dec] Mib [dec] Archive Init Failed [chars]

Explanation   Failed to initialize slot archive file.

Recommended Action   No action required.

Error Message   SPM-4-SPM_EPTDB_BAD: SPM database corrupt [chars]

Explanation   SPM database corruption.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SPM-7-RM_RAMDB_INIT: Resource Mgr Ram DB init failed [chars]

Explanation   Failed to initialize Resource RAM Database.

Recommended Action   No action required.

Error Message   SPM-7-SPM_TIMER_ERROR: Timer operation error [chars]

Explanation   Failed to start the timer.

Recommended Action   No action required.

Error Message   SPM-7-SPM_MEM_ERROR: Memory allocation error [chars]

Explanation   Failed to allocate memory.

Recommended Action   No action required.

Error Message   SPM-7-SPM_MSG_ERROR: Message send failed [chars]

Explanation   Failed to send message.

Recommended Action   No action required.

Error Message   SPM-7-SPM_ERR_GEN: [chars]

Explanation   General error.

Recommended Action   No action required.

Error Message   SPM-4-RM_API_ERROR: [chars] [dec] [dec]

Explanation   RM API parameter error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SPM-4-RM_NULL_PTR: EVENT_DUMP_TRACE EVENT_NO_ACTION [chars] is NULL

Explanation   NULL pointer in RM API.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SPM-4-SPM_BOTH_END_POINT_SAME_NSAP_VPI_VCI: [chars]: End points have same NSAP VPI and VCI FATAL ERROR: event SPM_BOTH_END_POINT_SAME_NSAP_VPI_VCI is more than 15 chars.

Explanation   End points are same. End point includes nsap, vpi and vci.

Recommended Action   No action required.

Service Resource Module (SRM) Messages

This section contains the Service Resource Module (SRM) messages.

Error Message   SRM-4-DBTBLINIT_ERR: Fail to register TBL [chars] NumElm=[dec] ElmSize=[dec] Upgrd=0x[dec]wngrd=0x

Explanation   Database Table initialization error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SRM-4-SRMCT_DBREG_ERR: Fail to registering [chars] data base type = [dec] version= [chars]

Explanation   Unable to register the SRM TASK data base SRMCT task will not be able to spawn properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SRM-4-DBTBLIDINVLD: [chars] Table [chars]: is invalid. Table type=[dec] idx =[dec]

Explanation   Unable to read/update data base entry because of invalid table ID SRMCT task will not be able to spawn properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SRM-4-DBTBLINVLD: [chars] Table [dec]: is invalid. Table type=[dec] idx =[dec]

Explanation   Unable to read/update data base entry because of invalid table ID SRMCT task will not be able to spawn properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SRM-4-SRMCT_INIT_ERR: Init Error: [chars]

Explanation   SrmComTask initialization error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SRM-7-SRMCT_CD_INS: Got SRM Card Insert Msg. from PMM Slot [dec]

Explanation   Card insertion notification.

Recommended Action   No action required.

Error Message   SRM-7-SRMCT_CD_REM: Got SRM Card Remove Msg. from PMM Slot [dec]

Explanation   Card removal notification.

Recommended Action   No action required.

Error Message   SRM-7-SRMCT_BC_INS: SRM Back Card inserted or detected Slot [dec]

Explanation   Successful back card detection.

Recommended Action   No action required.

Error Message   SRM-7-BC_MISSING: SRM Back Card missing or failed Slot [dec]

Explanation   Unable to detect the back card.

Recommended Action   No action required.

Error Message   SRM-7-UNKNOWN_STATE: SRMCT entered in unknown state. Slot [dec]

Explanation   SRM card in unknown state

Recommended Action   No action required.

Error Message   SRM-7-UNKNOWN_SRM: Unknown SRM card detected Slot [dec]

Explanation   Unknown SRM card detected.

Recommended Action   No action required.

Error Message   SRM-7-PIO_INIT_FAIL: SrmInit: Failed to initialise PIOs Slot [dec]

Explanation   PIO initialization failure.

Recommended Action   No action required.

Error Message   SRM-7-CARD_LOOSE: Card Loose

Explanation   SRM PIOs indicate that the card is not inserted properly.

Recommended Action   No action required.

Error Message   SRM-7-XIL_IMG_ID: SRM Xilinx IMG ID. for slot [dec] [chars]

Explanation   XIL image encountered.

Recommended Action   No action required.

Error Message   SRM-7-XIL_IMG_ERR: SRM Xilinx IMG Slot [dec] [chars]

Explanation   Function that gets XIL image failed.

Recommended Action   No action required.

Error Message   SRM-7-XIL_DNLD_FAIL: SRM Xilinx download failed Slot [dec]

Explanation   SRM XILINX down failed.

Recommended Action   No action required.

Error Message   SRM-7-SRMCT_FAIL_MSG: Received FAIL msg. from SRBM Task. Slot [dec]

Explanation   SRM card failure message received.

Recommended Action   No action required.

Error Message   SRM-7-INVALID_MSG: SrmMsgHandler: Rcvd. Invalid request

Explanation   Invalid SRM message received.

Recommended Action   No action required.

Error Message   SRM-7-CLR_SRM_CNF: Cleared SRM configuration

Explanation   Successful SRM clear configuration.

Recommended Action   No action required.

Error Message   SRM-7-CLR_SRM_CNF_ERR: Clear SRM configuration error: [chars]

Explanation   SRM configuration error.

Recommended Action   No action required.

Error Message   SRM-7-SRM_MISMATCH: SRM CARD MISMATCH:instance = [dec] HWREV= [hex] [chars]

Explanation   SRM CARD went in to Mismatch because this hardware revision is not supported in POPEYE

Recommended Action   No action required.

Error Message   SRM-7-LEGACY_ERR_RPT: Srbm Error Rpt: [chars]: [chars]

Explanation   Srbm error has occurred.

Recommended Action   No action required.

System Service Interface (SSI) Messages

This section contains the System Service Interface (SSI) messages.

Error Message   SSI-4-ARCH_ERROR: Archive Error : [chars]

Explanation   The archive file doesn't exist on the service module.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-PARMINVALID: Parm [chars] value '0x[hex]' is invalid to [chars].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-PARMMAXEXCEEDED: Parm [chars] '[dec]' has exceeded max [dec] to [chars].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function exceeded maximum value specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-PARMOUTOFRANGE: Parm [chars] '[dec]' is out of range [dec]-[dec] to [chars].

Explanation   API Software Error. The parameter value for the named parameter passed in as an argument to the named function is out of the specified range of values.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-6-RESETDUMPTRACE: A function trace dump is available from the last reset.

Explanation   A function trace dump has been saved which contains a trace of the operations being done before the current reset. If the reset was a watchdog timeout then this information will indicate what was happening when the watchdog occurred.

Recommended Action   No action required.

Error Message   SSI-3-EXCEPTION: Software Exception: Vector [dec] EPC: 0x[hex] ADDR: 0x[hex].

Explanation   A software exception has occurred. The vector number specifies the type of exception. The EPC is the program counter of the failing instruction. The address field is the address that was attempted to be accessed if a load or store TLB or Address exception. See the associated error log for additional information of the exception state.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-ISRNOTCALLABLE: Function [chars] cannot be called by Interrupt Service Routine.

Explanation   The named function was called by an interrupt service routine and it cannot perform any blocking function calls.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TBLSEMTAKEFAIL: Unable to take Vx semaphore [chars] table. Errno=[hex]

Explanation   The VxWorks semaphore used to protect the specified system table was not able to be taken. SSI may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-OBJCREATENOMEM: [chars] creation failed due to memory shortage in Vxworks partition.

Explanation   Creation of a Vxworks object failed due to a memory shortage in the VxWorks system memory partition.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMTBLFULL: The system semaphore table is full. All [dec] entries are used.

Explanation   The system semaphore table is full. There are no more entries available to create an SSI_SEMID. The system limit needs to be increased or dynamically created semaphores are not being deleted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMDAINVALID: Deadlock action [dec] is invalid to create SSI semaphore.

Explanation   An invalid deadlock action value was passed in as an argument to create an SSI semaphore.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMTYPEINVALID: Sem Type [dec] is invalid to create SSI semaphore.

Explanation   An invalid semaphore type value was passed in as an argument to create an SSI semaphore.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMOPTINVALID: Sem Option [dec] is invalid to create SSI semaphore of type [dec].

Explanation   An invalid semaphore option value was passed in as an argument to create an SSI semaphore.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMSTATEINVALID: Sem Initial State [dec] is invalid to create SSI semaphore.

Explanation   An invalid semaphore initial state value was passed in as an argument to create an SSI semaphore.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMCREATEFAIL: Semaphore creation failed. Errno=[hex].

Explanation   Creation of a semaphore failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMIDINVALID: An invalid SSI_SEMID of [chars] passed as an argument.

Explanation   An invalid SSI semaphore id was passed in as an argument into the function. The SSI_SEMID is in the incorrect format.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-5-SEMIDDELETED: SSI_SEMID [chars] deleted and no longer exists.

Explanation   The SSI semaphore id that was passed in as an argument is no longer valid. The SSI_SEMID probably has been deleted.

Recommended Action   No action required.

Error Message   SSI-5-SEMDELUNOWN: SSI_SEMID [chars] being deleted and is owned by another task

Explanation   The SSI semaphore id that is being deleted is not owned by the deleting task and could be owned by another task. A mutual exclusion semaphore should be taken before deletion.

Recommended Action   No action required.

Error Message   SSI-4-SEMDELFAIL: Delete of semaphore [dec]ed. Errno=[hex]

Explanation   The deletion of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly. Memory resources may have been lost.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMTAKEFAIL: Take of semaphore [dec]ed. Errno=[hex]

Explanation   The Take of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMGIVEUNOWN: SSI_SEMID [chars] not owned by giving task. It is owned by task

Explanation   The SSI semaphore id that is being given is not owned by the giving task and mutual exclusion semaphore can only be given by the owning task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMGIVEFAIL: Give of semaphore [dec]ed. Errno=[hex]

Explanation   The Give of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMFLUSHINV: SSI_SEMID [dec]ushed - operation invalid.

Explanation   The SSI semaphore id that is being flushed does not support the flush operation and should not be called.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-SEMFLUSHFAIL: Flush of semaphore [dec]ed. Errno=[hex]

Explanation   The Give of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQTBLFULL: The system message queue table is full. All [dec] entries are used.

Explanation   The system message queue table is full. There are no more entries available to create a SSI_MQID. The system limit needs to be increased or dynamically created message queues are not being deleted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQMAXINVALID: Max messages value [dec] is invalid to create SSI message queue.

Explanation   An invalid maximum number messages in the message queue was passed in as an argument to create an SSI message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQMLENINVALID: Message length [dec] is invalid to create SSI message queue.

Explanation   An invalid message length value was passed in as an argument to create an SSI message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQOWNERINVALID: Owning Task [chars] invalid to create SSI message queue.

Explanation   An invalid owner task id value was passed in as an argument to create an SSI message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQOWNERNOTEXIST: Owning Task [dec]oes not exist to own created SSI message queue.

Explanation   An nonexistent owner task id value was passed in as an argument to create an SSI message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQCREATEFAIL: Message Queue creation failed. Errno=[hex].

Explanation   Creation of a message queue failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQSEMCRTFAIL: Creation of sync semaphore for SSI_MQID failed. Errno=[hex]

Explanation   The creation of VxWorks semaphore used to synchronize multiple SSI_MQID message queues failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQIDINVALID: An invalid SSI_MQID of [chars] passed as an argument.

Explanation   An invalid SSI message queue id was passed in as an argument into the function. The SSI_MQID is in the incorrect format.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-5-MQIDDELETED: SSI_MQID [chars] deleted and no longer exists.

Explanation   The SSI message queue id that was passed in as an argument is no longer valid. The SSI_MQID probably has been deleted.

Recommended Action   No action required.

Error Message   SSI-4-MQQUOTAINVALID: Message queue quota value [dec] is invalid for SSI_MQID

Explanation   An invalid message queue quota value was passed in as an argument to set the quota on a SSI message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQSEMDELFAIL: Delete of sync semaphore [dec]ed. Errno=[hex]

Explanation   The deletion of VxWorks semaphore used to synchronize multiple SSI_MQID message queues failed unexpectedly. Memory resources may have been lost.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQDELFAIL: Delete of message queue [dec]ed. Errno=[hex]

Explanation   The deletion of VxWorks message queue used to implement the SSI_MQID failed unexpectedly. Memory resources may have been lost.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQFLSHRECVFAIL: Receive to flush Vx Message Queue [dec]ed. Errno=[hex].

Explanation   The receive on the VxWorks message queue to flush it failed unexpectedly. It could have been corrupted or deleted unexpectedly

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQSENDLENINV: Message length of [dec] to send to SSI_MQID [chars] invalid.

Explanation   An invalid message length value was passed in as an argument to send message to an SSI message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQSENDFAIL: Send to Vx msgQ [dec]ed. Errno=[hex]

Explanation   The send to VxWorks message queue used to implement the SSI_MQID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQSEMGIVEFAIL: Give of sync semaphore [dec]ed. Errno=[hex]

Explanation   The give of VxWorks semaphore used to synchronize multiple SSI_MQID message queues failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQISRSENDNZTO: Send to SSI_MQID [chars] done with timeout [dec] by ISR.

Explanation   The send to message queue was done by an Interrupt Service Routine with a non zero timeout value. ISRs cannot block.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQRECVLENINV: Message length of [dec] to receive from SSI_MQID [chars] invalid.

Explanation   An invalid message length value was passed in as an argument to receive message from an SSI message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQRECVFAIL: Receive from Vx msgQ [dec]ed. Errno=[hex]

Explanation   The receive from VxWorks message queue used to implement the SSI_MQID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQSEMTAKEFAIL: Take of sync semaphore [dec]ed. Errno=[hex]

Explanation   The give of VxWorks semaphore used to synchronize multiple SSI_MQID message queues failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQHNDLRINVALID: Msg Handler [chars] invalid to process msg for SSI_MQID

Explanation   An invalid message handler function pointer value was passed in as an argument to create an SSI message queue that requires a message handler.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQHNDLRFAIL: Msg Handler [dec]ed processing msg for SSI_MQID [hex]

Explanation   The message handler function returned failure while processing a message received in the SSI message queue.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQNUMMSGFAIL: Get num of msg in Vx msgQ [dec]ed. Errno=[hex]

Explanation   Getting the number of messages in the VxWorks message queue used to implement the SSI_MQID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQINFOPTRINV: Msg Info Ptr [chars] invalid to get info SSI_MQID

Explanation   An invalid message info structure pointer value was passed in as an argument to get SSI message queue information.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MQINFOFAIL: Get info about Vx msgQ [dec]ed. Errno=[hex]

Explanation   Getting the information about the VxWorks message queue used to implement the SSI_MQID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKTBLFULL: The system task table is full. All [dec] entries are used.

Explanation   The system task table is full. There are no more entries available to create a SSI_TID. The system limit needs to be increased or dynamically created tasks are not being deleted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKSEMGIVEFAIL: Give of sync semaphore [dec]ed. Errno=[hex]

Explanation   The give of VxWorks semaphore used to synchronize child SSI_TID initialization status with spawning parent failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-5-TASKINITPTO: SSI_TID [dec]nable to send init status because parent timed-out.

Explanation   The child SSI_TID was unable to send its initialization status to the spawning parent task as the parent timed-out and is no longer waiting for the child status.

Recommended Action   No action required.

Error Message   SSI-5-TASKINITFAIL: SSI_TID [dec]ization failed. Errno=[hex] - Task suspended.

Explanation   The SSI_TID failed to initialize properly and was suspended to prevent further errors.

Recommended Action   No action required.

Error Message   SSI-4-TASKIDINVALID: An invalid SSI_TID of [chars] passed as an argument.

Explanation   An invalid SSI task id was passed in as an argument into the function. The SSI_TID is in the incorrect format.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-5-TASKIDDELETED: SSI_TID [chars] deleted and no longer exists.

Explanation   The SSI task id that was passed in as an argument is no longer valid. The SSI_TID probably has been deleted.

Recommended Action   No action required.

Error Message   SSI-4-TASKDELFAIL: Delete of task [dec]ed. Errno=[hex]

Explanation   The deletion of VxWorks task used to implement the SSI_TID failed unexpectedly. Memory resources may have been lost.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-5-TASKDELSAFE: SSI_TID [chars] safe from deletion and is suspended.

Explanation   The SSI task id that was passed in as an argument is safe from being deleted and it is also suspended. Task may have suspended on an exception after taking a task safe mutual exclusion semaphore.

Call to delete task is failed rather than cause hang condition to caller.

Recommended Action   No action required.

Error Message   SSI-4-TASKRESUMEFAIL: Resume of task [dec]ed. Errno=[hex]

Explanation   The resumption of VxWorks task used to implement the SSI_TID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKSUSPENDFAIL: Suspend of task [dec]ed. Errno=[hex]

Explanation   The suspension of VxWorks task used to implement the SSI_TID failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-5-TASKSUSPENDSAFE: SSI_TID [chars] safe from deletion could be holding semaphores.

Explanation   The SSI task id that was passed in as an argument is safe from being deleted. The task may be holding a mutual exclusion semaphore and should not be suspended. Suspension could result in a deadlock of the system. Suspension is failed rather than cause hang condition to system.

Recommended Action   No action required.

Error Message   SSI-4-TASKPRIOINVALID: Task priority value [dec] is invalid to create SSI task.

Explanation   An invalid task priority number was passed in as an argument to create an SSI task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKPGRPINVALID: Task priority group [dec] is invalid to create SSI task.

Explanation   An invalid task priority group was passed in as an argument to create an SSI task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKAPPLINVALID: Task application id value [dec] is invalid to create SSI task.

Explanation   An invalid task application id value was passed in as an argument to create an SSI task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKSTKSIZEINV: Task stack size value [dec] is invalid to create SSI task.

Explanation   An invalid task stack size value was passed in as an argument to create an SSI task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKSUSPACTINV: Task suspended action value [dec] is invalid to create SSI task.

Explanation   An invalid task suspend action value was passed in as an argument to create an SSI task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKFAILACTINV: Task fail action value [dec] is invalid to create SSI task.

Explanation   An invalid task fail action value was passed in as an argument to create an SSI task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKSEMCRTFAIL: Creation of sync semaphore for SSI_TID failed. Errno=[hex]

Explanation   The creation of VxWorks semaphore used to synchronize SSI_TID initialization with parent failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TASKSPAWNFAIL: Task spawn failed. Errno=[hex].

Explanation   Spawning of a task failed unexpectedly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-5-TASKINITACKTO: SSI_TID [dec] out initialization of child SSI_TID

Explanation   The parent SSI_TID timed out the send of initialization status from the child task. Either child task had problems or didn't wait long enough.

Recommended Action   No action required.

Error Message   SSI-4-TASKWACKFAIL: Failed to wait for init status from child SSI_TID [hex]

Explanation   The parent SSI_TID was unable to wait for the send of initialization status from the child task.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-5-TASKDELMQOWN: SSI_TID [chars] being deleted and still owns message queues.

Explanation   The SSI task id that is being deleted still owns message queues. These message queues should be deleted before the task is deleted if the task is not being recovered.

Recommended Action   No action required.

Error Message   SSI-4-INVPPARTPTR: The private partition structure has not been allocated.

Explanation   The private partition structure which holds information about the partitions has not been allocated. This indicates a software problem (ssiMemPartInit has not been called, or the pointer has been overwritten).

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-THREEPART: Attempted to create [dec] partitions only 3 allowed.

Explanation   An attempt was made to create an invalid number of partitions. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MALLOC: Could not create partition info structure errno [dec].

Explanation   An error was returned by malloc when attempting to allocate the partition info structure.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-NOSEMAPHORE: Could not create a semaphore to partition [dec] errno [dec].

Explanation   An error was returned by semBCreate when attempting to create a semaphore.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVTYPE: The requested memory type is invalid [dec].

Explanation   An attempt was made to allocate memory with a memory type parameter that is invalid. This indicates a software problem

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVOPTION: The requested options flag is invalid [dec].

Explanation   An attempt was made to allocate memory with an options flag parameter that is invalid. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-ZEROSIZE: A request for 0 bytes was made.

Explanation   An attempt was made to allocate 0 bytes. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVLENGTH: The requested length [dec] is greater than partition 0x[hex] size [dec].

Explanation   An attempt was made to allocate more memory than what is allocated for the partition.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-NOPARTINFO: An error was returned when trying to get partition info errno [dec].

Explanation   While attempting to get the partition statistics, memPartInfoGet returned an error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-BELOWTHRES: The number of free bytes [dec] is below the set threshold [dec] for partition [dec].

Explanation   While attempting to allocate low priority memory, the number of free bytes is below the set threshold.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-NOPARTITION: Could not allocate [dec] bytes from partition 0x[hex] errno [dec].

Explanation   An error was returned by memPartAlloc while attempting to allocate memory.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-NOTOWNER: A process 0x[hex] that is not the owner 0x[hex] is attempting to free block 0x[hex]

Explanation   A process that is not the owner of allocated memory is attempting to deallocate the memory. This indicates a software error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MEMPARTCREATE: An error was returned trying to create the partition 0x[hex] errno [dec]

Explanation   An error was returned by memPartCreate while attempting; to create the specified partition.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MEMPARTFREE: An error was returned trying to deallocate memory block at 0x[hex] errno [dec]

Explanation   An error was returned by memPartFree while attempting to deallocate memory.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-STRANGEADDR: The memory address 0x[hex] is not within any of the partitions.

Explanation   The memory address is not within any of the partitions. This indicates a bad address or possible corruption of the memory partition structure.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   Error Message SSI-4-CKINVLIST: Invalid sysChunkPoolList address 0x[hex] not on word boundary.

Explanation   The memory block address is not on a word boundary

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CKINVWRDADD2: Invalid memory block address 0x[hex] noton a word boundary.

Explanation   The memory block address is not on a word boundary

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CKINVWRDADD: EVENT_RUN_LOG_FUNC ssiMemChunkData Invalid memory block address 0x[hex] not on a word boundary.

Explanation   The memory block address is not on a word boundary

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-PTINVWRDADD: EVENT_RUN_LOG_FUNC ssiMemData Invalid memory block address 0x[hex] not on a word boundary.

Explanation   The memory block address is not on a word boundary

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVMEMTYPE: EVENT_STKTRC | EVENT_RUN_LOG_FUNC ssiMemData Invalid memory type [dec] for memory block at 0x[hex].

Explanation   The memory type stored in the header of the block is wrong. This indicates that the header has been corrupted or is invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVLENGTH1: EVENT_RUN_LOG_FUNC ssiMemData Invalid length for memory block at 0x[hex] owner 0x[hex] caller 0x[hex].

Explanation   The length stored by VxWorks is wrong. This indicates that memory has been corrupted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVMAGICCOOKIE: EVENT_RUN_LOG_FUNC ssiMemDataInvalid magic number 0x[hex] for memory block at 0x[hex].

Explanation   The magic number stored at the end of the block is wrong. This indicates that memory has been corrupted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVREFCOUNT: EVENT_RUN_LOG_FUNC ssiMemData Memory block at 0x[hex] is not allocated reference count = 0

Explanation   The reference count for the block is 0. This indicates that the block has already been freed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVVXWORKPART: EVENT_RUN_LOG_FUNC ssiMemData Invalid partition index [dec] for memory block at 0x[hex]

Explanation   The partition index in the header is invalid. This block was allocated from the VxWorks memory heap and this should be ab1ebeef. This indicates that the header has been corrupted or is invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVPARTINDEX: EVENT_RUN_LOG_FUNC ssiMemData Invalid partition index [dec] for memory block at 0x[hex]

Explanation   The partition index in the header is invalid. This indicates that the header has been corrupted or is invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-DOWNSTATIC: Not enough memory in the dynamic pool for [dec] bytes trying static

Explanation   The dynamic partition does not have enough space to allocate the specified number of bytes. The software will try to allocate the space from the static partition.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-DOWNVXWORKS: Not enough memory in the static pool for [dec] bytes trying VxWorks' heap

Explanation   The static partition does not have enough space to allocate the specified number of bytes. The software will try to allocate the space from the VxWorks heap.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-INVPARTADDR: EVENT_RUN_LOG_FUNC ssiMemData Invalid address 0x[hex] for partition [dec] start:0x[hex] length:0x[hex]

Explanation   The address is not within the range of the partition stored in the header. This indicates that the header has been corrupted or is invalid.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-NOCHUNKSEMA: Couldn't create the mutex semaphore needed by the chunk memory manager [dec].

Explanation   The chunk memory manager could not create the mutex semaphore necessary for its operation.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-NOCHUNKMEMALLOC: Couldn't allocate the memory for the pool.

Explanation   An error was returned by ssiMalloc when attempting to allocate the memory for the pool.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKSIZE: The calculate pool size [dec] is greater than the allocated memory size [dec].

Explanation   The required memory size was not allocated for this pool. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKSEMTAKE: Couldn't take the mutex semaphore errno [dec].

Explanation   An error occurred when trying to acquire the mutex. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKSEMGIVE: Couldn't release the mutex semaphore errno [dec].

Explanation   An error occurred when trying to release the mutex. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKPOOLINUSE: The operation could not be tried because the pool is in use.

Explanation   The pool operation could not be tried because the pool is in use.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKINVID: The pool ID 0x[hex] is invalid.

Explanation   The pool ID is invalid. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKSHORTAGE: The pool 0x[hex] doesn't have a chunk to allocate.

Explanation   The specified pool cannot allocate the requested chunks. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKINVPTR: The chunk pointer is invalid.

Explanation   The chunk pointer is invalid. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKNOTALLOC: The chunk 0x[hex] is not allocated.

Explanation   The chunk is not allocated. This indicates a software problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKMAGICCKE: EVENT_RUN_LOG_FUNC ssiMemChunk Invalid magic number 0x[hex] for memory block at 0x[hex].

Explanation   The magic number stored at the end of the block is wrong. This indicates that memory has been corrupted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKNOTPOOL: EVENT_RUN_LOG_FUNC

ssiMemChunkData The memory chunk at 0x[hex] has an invalid poolID 0x[hex].

Explanation   The memory chunk specifies a nonexistant pool ID This indicates that memory has been corrupted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKDIFPOOL: EVENT_RUN_LOG_FUNC ssiMemChunkData The memory chunk at 0x[hex] is not from pool 0x[hex].

Explanation   The memory chunk is not within the pool specified by the pool ID. This indicates that memory has been corrupted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-CHUNKNOTOWNER: A process [dec] that is not the owner [dec] is attempting to free block 0x[hex]

Explanation   A process that is not the owner of allocated memory is attempting to deallocate the memory. This indicates a software error.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERTBLFULL: The system timer table is full. All [dec] entries are used.

Explanation   The system timer table is full. There are no more entries available to create a SSI_TIMERID. The system limit needs to be increased or dynamically created tasks are not being deleted.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERHANDLER: Attempt to create a system timer with invalid handler.

Explanation   An attempt was made to create a system timer with an invalid handler function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERNOCREATE: Unable to create Vx POSIX timer. Errno=[hex]

Explanation   An attempt to create a Vx POSIX timer failed. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERNOCONNECT: Unable to connect handler functionto Vx POSIX timer. Errno=[hex]

Explanation   An attempt to create a Vx POSIX timer failed. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERNOCANCEL: Unable to cancel Vx POSIX timer. Vx Timer=[hex]

Explanation   An attempt to cancel a Vx POSIX timer failed. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERNODELETE: Unable to delete Vx POSIX timer. Vx Timer=[hex]

Explanation   An attempt to delete a Vx POSIX timer failed. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERINVALIDID: SSI function called with invalid ID. SSI Timer=[hex]

Explanation   An SSI function was called with an invalid timer ID. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERINVALIDENT: SSI function called with invalid entry. SSI Timer=[hex] Vx Timer=[hex]

Explanation   An SSI function was called for an invalid timer entry. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERINVALIDTSK: Attempt to manipulate timer by non-owning task. SSI Timer=[hex] Task=[hex]

Explanation   An SSI function was called to operate on a timer entry by a non-owning task. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERINVALIDVAL: Function called with invalid time value. Time val=[hex]

Explanation   An SSI function was called with an invalid timer value. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERNOSETGET: An attempt to set or get a timer value failed. Time val=[hex]

Explanation   An SSI function call to either set or get the. timer value failed. SSI timers may not be initialized properly.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERSIGERROR: An attempt to manipulate a signal failed. SSI Timer=[hex]

Explanation   An SSI function call to manipulate a POSIX signal failed. This indicates corruption has occurred.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TIMERINVTOD: An attempt to read the system time-of-day failed.

Explanation   The function call to get the current time-of-day failed. This indicates corruption has occurred.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-MKTIMEFAIL: Mktime failed in [chars]. errno=[hex].

Explanation   The function call to mktime to convert a broken down time to an integer second count failed with the error code specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-PUTENVFAIL: Putenv of string '[chars]' failed in [chars]. errno=[hex].

Explanation   The function call to putenv to put a variable into the environment failed with the error code specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-WDCREATEFAIL: SSI [chars] watchdog create failed in [chars]. errno=[hex].

Explanation   Unable to create the specified watchdog for the specified use in the named function. It failed with the specified error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-WDSTARTFAIL: SSI [chars] watchdog start failed in [chars]. rc=[dec] errno=[hex].

Explanation   Unable to start the specified watchdog for the specified use in the named function. It failed with the specified return code and error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TMRCANCELINV: SSI Timeout event not found in [chars]. TmoFunc=[hex].

Explanation   The specfied timeout event could not be found in the named function. The value of the Timeout function and key are specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TMRNOTINIT: SSI Sync Timer not initialize for Task [dec]l [chars].

Explanation   The synchronous timeout facility was not initialized for the calling task before it tried to call the specified function. Initialization must be called before calling the function.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SSI-4-TMRHNDLRFAIL: Sync Timeout Handler [dec]ed in [chars]. key=[hex] rc=[dec] errno=[hex].

Explanation   The specified timeout handler function failed in the specified function. It was passed the specified key. The function failed with the specified return code and error number.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

System Module (SYS) Messages

This section contains the System Module (SYS) messages.

Error Message   SYS-7-STARTUP: System is up and the Reset Reason is: [[chars]]

Explanation   System started after reset.

Recommended Action   No action required.

Error Message   SYS-7-VERSION: Boot Code Rev: [[chars]] FW Rev: [[chars]]

Explanation   Version of Backup Boot and runtime FW image.

Recommended Action   No action required.

Error Message   SYS-2-TASKINITFAIL: Task[[chars]] failed of spawning

Explanation   Failed to spawn task.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-1-TASKHOLDCPU: Task[[chars]] is holding CPU

Explanation   System has detected a ready task.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-1-NOTASKHOLDCPU: unknown Task is holding CPU

Explanation   System has detected a task that is ready but not using the CPU.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-1-RTTASKSUSPEND: Root Task is suspended due to task spawn NAK/timeout

Explanation   The Root Task is suspended, because of a NAK or timeout trying to spawn the static tasks.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-1-BKTASKSUSPEND: Background Task is suspended and could not restart

Explanation   The Background Task is suspended, and could not restart.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-6-BKTASKRESTART: Background Task is suspended and restart is successful

Explanation   The Background Task got suspended, and restart is successful.

Recommended Action   No action required.

Error Message   SYS-1-TASKLOSTFATAL: Trouble-Task[[chars]]: action is SYSTEM RESET

Explanation   A task has disappeared or suspended, and could cause system RESET.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-3-TASKLOST: Trouble-Task[[chars]]: action is [chars]

Explanation   A task has disappeared or suspended.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-2-RECVTASKFAIL: Failed to [chars] Task[[chars]]

Explanation   A task has disappeared or suspended, and SYSTEM is not RESET

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-3-WRONGTYPTKRECV: Wrong Type[[dec]] to recv task[[chars]}

Explanation   taskRecover(): wrong type to recover a task.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-1-FILEOPENFAIL: failed to open event log file

Explanation   Failed to open event log file.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-3-WRNGEVTLOG: Error Task receives a message other than ERR_LOG_MSG

Explanation   Error Task has received a message other than the message type of ERR_LOG_MSG.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-2-PRIADJFAIL: Failed to adjust the priority Task[[chars]} TaskId[[dec]]

Explanation   Failed to adjust the priority for a task.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-2-NOFNDPRITSK: Failure to find the highest priority ready task

Explanation   Failure to find the highest priority ready task in trGet().

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-3-BRAMFAIL: BRAM checksum failed: [dec]d [dec]d

Explanation   BRAM checksum failed.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-2-EXCEPTION: [chars]

Explanation   Exceptional Interrupt occurred.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-3-NOVRAM_1: [dec]

Explanation   Invalid card type.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-2-NOVRAMFAIL: Novram on [chars] has checksum failure: [dec]d [dec]d

Explanation   BRAM checksum failed.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-7-TEST_DUMP: [chars]

Explanation   Test for Dump Trace.

Recommended Action   No action required.

Error Message   SYS-7-TEST_STACK: [chars]

Explanation   Test for Stack Trace.

Recommended Action   No action required.

Error Message   SYS-7-TEST_DUMPSTK: [chars]

Explanation   Test for Stack Trace and Dump Trace.

Recommended Action   No action required.

Error Message   SYS-7-TEST_BRAM: [chars]

Explanation   Test for BRAM and Stack Trace and Dump Trace.

Recommended Action   No action required.

Error Message   SYS-7-TIMECHANGE: Time changed - Old Date/Time: [dec]/[dec]/[dec] [dec]:[dec]:[dec]

Explanation   This information event indicates that the date or time for the shelf has been updated. The new time is the timestamp on the event while the old time is given in the message.

Recommended Action   No action required.

Error Message   SYS-7-ZONECHANGE: Time zone changed - New: [chars]Offset [dec] Old: [chars]Offset [dec]

Explanation   This information event indicates that the time zone information for the shelf has been updated. The new and old time zone information is given in the message.

Recommended Action   No action required.

Error Message   SYS-4-MSGINVALID: Received invalid msg to [chars]. Size=[dec] Msg=[hex] [hex] [hex] [hex] [hex]

Explanation   The message received by the specified function as a parameter is invalid. The message size and contents are specified.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-3-MSGPROCFAIL: Processing log messages failed [dec] consecutive times. errno=[hex]

Explanation   The processing of log messages failed the specified number of consecutive times. There is a problem with the received messages or the receiving message queue. The last time failed with the specified error number.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-7-LOGMSGCOUNTS: Log Message Counts: Evts [dec] Errs [dec] Inv [dec] EvtSave [dec] ErrSave [dec]

Explanation   The following counts were accumulated for processing of log messages. The first count is the number of event messages processed. The second count is the number of error messages processed. The third count is the number of invalid messages received. The fourth count is the number of times event save has failed. The fifth count is the number of times error saving has failed.

Recommended Action   No action required.

Error Message   SYS-3-EVENTSAVEFAIL: Saving events to disk failed [dec] consecutive times. errno=[hex]

Explanation   The saving of events to disk failed the specified number of consecutive times. There is a problem with saving the events to disk. The last time failed with the specified error number.

Recommended Action   Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   SYS-7-SAVEFAILCOUNTS: Save Fail Counts: Total [dec] Open [dec] Creat [dec] Seek [dec] Write [dec] Flush [dec]

Explanation   The following counts were accumulated for saving events to disk. The first count is the total number of saves that failed. The second count is the number of event file opens that failed. The third count is the number of event file creates that failed. The fourth count is the number of event file seeks that failed. The fifth count is the number of event file writes that failed. And the sixth count is the number of event file flushes that failed.

Recommended Action   No action required.

Error Message   SYS-7-BOOTREGISTERS: Boot ResetType=0x[hex] PioInputs=0x[hex] ResetPc=0x[hex] StatusReg=0x[hex] CauseReg=0x[hex] CacheErr=0x[hex]

Explanation   The values of the registers whenever a boot of the card happens. This gives detailed information what the state of the CPU was when the reset occurred.

Recommended Action   No action required.

Error Message   SYS-4-NETWORKUPERROR: Unable to activate [chars] interface.

[chars] failederrno=[hex]

Explanation   The specified network interface failed to activate for the reason specified. It failed with the specified error number. This error could be due an incorrect IP configuration for the specified interface.

Recommended Action   No action required.

Error Message   SYS-4-NETSTANDBYERROR: Unable to start standby ethernet

interface. [chars] failederrno=[hex]

Explanation   The standby Ethernet network interface failed to activate for the reason specified. It failed with the specified error number. This error could be due an incorrect IP configuration for the bootChange Ethernet values.

Recommended Action   No action required.

Error Message   SYS-4-IPCNFDBERROR: Ip Config Db Error. [chars] failed in [chars]. Errno=[hex]

Explanation   The IP configuration RAM database had the specified database error in the function specified. It failed with the specified error number.

Recommended Action   No action required.

Trivial File Transfer Protocol (TFTP) Messages

This section contains the Trivial File Transfer Protocol (TFTP) messages.

Error Message   TFTP-4-SOCKET_ERR: [chars]: Failed to Receive on Socket : [dec]

Explanation   Received error while trying to read data from TFTP socket.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   TFTP-4-TASK_SPAWN_ERR: [chars]: Spawn Task Failed TaskName: [chars] TaskPriority: [dec]

TaskStackSize: [dec]

Explanation   Spawning of a task failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

VSM Connection Management (VCNM) Messages

This section contains the VSM Connection Management (VCNM) messages.

Error Message   VCNM-4-INIT_FAIL: VCNM : pipc port create failed : err [dec]

Explanation   Initialization failure.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VCNM-7-UNKNOWN_MSG: VCNM : Unknown pipc message received msgType = [dec]

Explanation   Unknown message received.

Recommended Action   No action required.

Error Message   VCNM-7-UNKNOWN_TASK: VCNM : Message received with Invalid Task Id = [dec]

Explanation   Event received from unknown task.

Recommended Action   No action required.

Virtual Switch Interface (VSI) Messages

This section contains the Virtual Switch Interface (VSI) messages.

Error Message   VSI-4-VSI_MSG_LENGTH: VSI_MSG_LENGTH: [chars]

Explanation   VSI msg length problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSI_PG_LENGTH: VSI_PG_LENGTH: functionCode[hex] pgFmtId[hex]

Explanation   VSI pg length problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-SYNTAX_ERROR: VSI_SYNTAX_ERROR: functionCode[hex] msgStatus[hex]

Explanation   Syntax error in parsing VSI message problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSI_CONTROLLER: VSI_CONTROLLER: [chars]

Explanation   VSI Controller Problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSI_SAP: VSI_SAP: [chars]

Explanation   VSI SAP problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSI_MSGQ: VSI_MSGQ: [chars]

Explanation   VSI msg queue problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSI_SOCKET: VSI_SOCKET: [chars]

Explanation   VSI socket problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSI_UNKNOWN_CMD: VSI_UNKNOWN_CMD: [hex]

Explanation   Unknown VSI command.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSIS_TRAP: VSIS_TRAP: [chars] [dec]

Explanation   VSI Slave trap problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-7-VSIS_TX: VSIS_TX: [chars]

Explanation   VSI Slave transport problem.

Recommended Action   No action required.

Error Message   VSI-7-NULL_PTR: NULL_PTR at [chars]

Explanation   NULL pointer

Recommended Action   No action required.

Error Message   VSI-4-MALLOC_FAIL: MALLOC_FAIL

Explanation   ssiMalloc() failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-FREE_FAIL: FREE_FAIL

Explanation   ssiFree() failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-FBALLOC_FAIL: MALLOC_FAIL

Explanation   ssiFrameBufferAlloc() failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-FBFREE_FAIL: FREE_FAIL

Explanation   ssiFrameBufferFree() failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSI_TIMER: VSI_TIMER: [chars]

Explanation   VSI timer problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-4-VSI_CLK: VSI_CLK: [chars]

Explanation   VSI clock source problem.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSI-7-SSI_VSI_IF: SSI_VSI_IF: [chars]

Explanation   SSI VSI IF problem.

Recommended Action   No action required.

Virtual Service Module (VSM) Messages

This section contains the Virtual Service Module (VSM) messages.

Error Message   VSM-4-DISK_UPD_FAIL: VSM : [chars] : PXM Disk Update Failed

Explanation   Disk update failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSM-4-VSM_UNDO_DEL_BBIF_FAILED: VSM : [chars] : Undo Port delete Failed FATAL ERROR: event VSM_UNDO_DEL_BBIF_FAILED is more than 15 chars.

Explanation   Undo port delete failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSM-4-VSM_UNDO_MOD_BBIF_FAILED: VSM : [chars] : Undo Port modify Failed FATAL ERROR: event VSM_UNDO_MOD_BBIF_FAILED is more than 15 chars.

Explanation   Undo port modify failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSM-4-VSM_UNDO_BBIF_FAILED: VSM : [chars] : Undo Port Failed FATAL ERROR: event VSM_UNDO_BBIF_FAILED is more than 15 chars.

Explanation   Undo Port failed.

Recommended Action   Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the dsperr output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message   VSM-7-VSM_BBIF_ADDED: VSM : Broadband Interface [dec] Added

Explanation   BBIF successfully added.

Recommended Action   No action required.

Error Message   VSM-7-VSM_BBIF_DEL: VSM : Broadband Interface [dec] Deleted

Explanation   Deleted BBIF successfully.

Recommended Action   No action required.

Error Message   VSM-7-VSM_BBIF_MOD: VSM : Broadband Interface [dec] Modified

Explanation   Modified BBIF successfully.

Recommended Action   No action required.

Error Message   VSM-7-VSM_RSC_CNF_CHG: VSM : Conf Chg in Rsc Partition: ifNum [dec] ctrlr [dec] rowStat [dec]

Explanation   Configuration change occurred.

Recommended Action   No action required.

Error Message   VSM-7-BBCHAN_ADDED: VSM : Broadband Channel [dec] Added

Explanation   BB channel has been successfully added.

Recommended Action   No action required.

Error Message   VSM-7-BBCHAN_DELETED: VSM : Broadband Channel [dec] Deleted

Explanation   BB channel has been successfully deleted.

Recommended Action   No action required.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Nov 23 13:18:37 PST 1999
Copyright 1989-1999©Cisco Systems Inc.