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.

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.

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.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

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

Explanation Unknown/Invalid Board Id.

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

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

Explanation The given CBC Slot is unmapped and invalid.

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

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

Explanation cbcIN(y/present deasserted.

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

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

Explanation Physical slot not configured to Logical slot.

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

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

Explanation Unable to write to CBD chip.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

CHS-4-CHS_INIT_ERR: CHS : Task Init Failed

Explanation Channel initialization failed.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

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

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

Action No action required.

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

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

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

Card Management Mode (CMM) Messages

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

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

Explanation CMM/VSM initialization error.

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

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

Explanation Error in receiving message.

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

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

Explanation Error in receiving event.

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

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

Explanation Unknown message received.

Action No action required.

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

Explanation Error in sending a message.

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

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

Explanation Error in receiving messages.

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

Database Manager (DBM) Messages

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 API Software Error. The named parameter passed in as an argument to the named function had an invalid character in the string.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 API Software Error. The parameter value for the named parameter passed in as an argument to the named function exceeded maximum value specified.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

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

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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The specified callback function for the specified table failed with the return code specified. The function address which failed is also specified.

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

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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

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

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

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

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

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.

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

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.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to take the specified semaphore for the specified database in the named function. It failed with the specified return code and error number.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to create the specified pipc port in the named function. It failed with the specified return code and error number.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to get a pipc memory buffer. It failed with the specified return code and error number.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to send a pipc message of the specified type to other PXM card. It failed with the specified return code and error number.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to allocate the specified memory buffer for the specified database in the named function. It failed with the specified error number.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to spawn the specified task in the named function. It failed with the specified rc and error number.

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

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

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.

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

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.

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

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.

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

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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to remove directory tree for the specified database in the named function.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The processing of the specified message for the specified database has failed in the named function. See previous event for detailed failure information.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The sending of the specified message for the specified database has failed in the named function. See previous event for detailed failure information.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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 file system could also have a problem.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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 file system could also have a problem.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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 file system could also have a problem.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The specified disk table file has been corrupted by data being changed during a write. The commit of the update has been aborted.

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.

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The specified sequence number in the message passed as parameter to the named function was invalid. The correct value is specified.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Internal Messaging Error. The field value for the named parameter passed in as an argument to the named function was invalid.

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

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.

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.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The specified operation on a database file failed with the specified error number. There could be a problem with the disk or file system.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The specified operation on a database directory failed with the specified error number. There could be a problem with the disk or file system.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Internal API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Internal API Software Error. The parameter value for the named parameter passed in as an argument to the named function exceeded maximum value specified.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

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

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

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

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

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

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

Explanation Firmware download failed.

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

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

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

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The specified function call failed. It failed with the specified return code.

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

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

Explanation HSB Ram DB initialization failed.

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

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

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

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

Explanation Standby Ram update failed. Invalid action requested.

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

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

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

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

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

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

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

Explanation Downloading of the configuration to the card failed.

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

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

Explanation The configuration for the given slot was not found.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

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

Explanation Unable to create message queues during initialization.

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

ILMI-4-BAD_SNMP_VER: ILMI_BAD_SNMP_VERSION: [chars]

Explanation Bad SNMP version.

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

ILMI-4-ILMI_PARSE_ERR: ILMI_AUTH_PARSE_ERR: [chars]

Explanation SNMP community string purser error.

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

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

Explanation Unknown message type received.

Action No action required.

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

Explanation Error during sending a message.

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

ILMI-4-RCV_MSG_ERROR: ILMI_RCV_MESSAGE_ERROR : [chars]

Explanation Error in receiving a message.

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

ILMI-4-INV_COMM_STR: ILMI_INVALID_COMM_STRING: [chars]

Explanation Invalid ILMI community string.

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

ILMI-4-ILMI_ASN1_ERR: ILMI_ASN1_PARSE_ERR: [chars]

Explanation PDU paring function returned error.

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

ILMI-4-INVALID_PDU: ILMI_INVALID_PDU_TYPE: [chars]

Explanation Received an invalid PDU.

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

ILMI-4-ILMI_TRAP_ERROR: ILMI_TRAP_ERROR: [chars]

Explanation Error in ILMI trap.

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

ILMI-4-MAKE_OCTET_ERR: ILMI_MAKE_OCTET_ERROR: [chars]

Explanation Error in making octet string.

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

ILMI-4-MAKE_PDU_ERR: ILMI_MAKE_PDU_ERROR: [chars]

Explanation Error PDU building function returned error.

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

ILMI-4-MAKE_VARBND_ERR: ILMI_MAKE_VAR_BIND_ERROR: [chars]

Explanation Error in making Var Bind.

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

ILMI-4-CLONE_OID_ERR: ILMI_CLONE_OID_ERROR: [chars]

Explanation Clone Enterprise failed.

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

ILMI-4-MAKE_AUTH_ERR: ILMI_MAKE_AUTHENT_ERROR: [chars]

Explanation Error in authenticating the community string.

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

ILMI-4-ILMI_SNMP_ERR: ILMI_SNMP_ERROR: [chars]

Explanation SNMP related error happened.

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

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

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

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

ILMI-4-TBL_OVERFLOW: ILMI_PREFIX_TBL_OVERFLOW: [chars]

Explanation ILMI PrefixTable overflow.

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

ILMI-4-ILMI_MSG_ERR: ILMI_MSG_ERROR: [chars]

Explanation Error during sending a message.

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

ILMI-4-BUFALLOC_FAIL: ILMI_TX_BUFF_ALLOC_FAILS: [chars]

Explanation Memory not available.

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

ILMI-4-ILMI_OUT_OF_BUF: ILMI_OUT_OF_BUF : [chars]

Explanation Unable to allocate SAR buffer.

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

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

Explanation Frame transmission function returned error.

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

ILMI-4-SEM_GET_ERR: SEMAPHORE_GET_ERROR [chars]

Explanation Error while taking a semaphore.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

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

Explanation Initialization error in upgrade task.

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

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

Explanation Wrong event received.

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

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

Explanation Error in receiving messages.

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

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

Explanation Error in allocating a buffer.

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

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

Explanation Bad event received.

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

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

Explanation Unknown message type received.

Action No action required.

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

Explanation Error in sending a message.

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

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

Explanation Error in receiving a message.

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

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

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

Explanation NAK message received notification.

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

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

Explanation Invalid card message.

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

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

Explanation Error in receiving a CLI message.

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

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

Explanation Error in sending a CLI message.

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

INST-7-RESET: EVENT_WRITE_BRAM EVENT_NO_ACTION [chars]

Explanation Other PXM has successfully been reset.

Action No action required.

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

Explanation Starting the abort of all processes.

Action No action required.

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

Explanation Downloading FW to a card failed.

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

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

Explanation Downloading Firmware notification.

Action No action required.

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

Explanation Downloading of Firmware is successful.

Action No action required.

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

Explanation Change of state notification.

Action No action required.

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

Explanation Change of state notification.

Action No action required.

INST-7-COMMAND0: [chars]

Explanation rstupgrade command notification.

Action No action required.

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

Explanation Beginning of install.

Action No action required.

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

Explanation Notification of setting primary/secondary PXM image.

Action No action required.

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

Explanation install command notification.

Action No action required.

Line Driver (LDRV) Messages

This section contains the Line Driver (LDRV) messages.

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to update the configuration data base because of the invalid DB version number.

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

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

Explanation Requested function detected invalid Port number passed.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The DC identification bits are invalid for number of RCMP connection.

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

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

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

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

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Statistical alarm has been switched to a new state. The severity can be Major, Minor or Clear.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Plcp alarm has been switched to a new state. The severity can be Major, Minor or Clear.

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

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.

Action No action required.

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.

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

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

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

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

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

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

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

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

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

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

LDRV-5-MISDIRECTEDMSG: Misdirected message [dec]

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

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Sonet Line number does not match with the configuration database.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Invalid section Trace Number is detected in the configuration. Line Driver will reset config to default value.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Invalid statSeverity/lineAlmCfg is detected in the configuration. Line Driver will reset config to default value.

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

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.

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

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

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 dsx3LineLength not in the range of 1-255. Line Driver will reset config to default value.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to register the Line Driver data base. Ldrv task will not be able to spawn properly.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to register a table entry into the database. Ldrv task will not be able to spawn properly.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to read/update database entry because of invalid table ID. Ldrv task will not be able to spawn properly.

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

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.

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

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.

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

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.

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

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.

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

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

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

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

Explanation Inband recovered clock has invalid line number.

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

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

Explanation Inband Frame Pulse Clock has invalid line number.

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

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

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

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

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

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.

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

Action No action required.

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

Explanation Invalid parameters passed into function.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Inter Process Communication (PIPC) Messages

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

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

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

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

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

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

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

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

Explanation Synchronization request between requested slots failed.

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

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

Explanation Buffer allocation failed.

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

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

Explanation Message error happened during sending a response.

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

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

Explanation Error happened in sending a message.

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

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

Explanation PMM time out.

Action No action required.

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

Explanation Application Timer Add function failed.

Action No action required.

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

Explanation Card assuming Mastership.

Action No action required.

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

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

Action No action required.

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Invalid state or received invalid event as an input parameter.

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

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

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

Action No action required.

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

Explanation Error occurred while trying to go active.

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

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

Explanation Resetting either Master or the Slave.

Action No action required.

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

Explanation Database update failed.

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

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

Explanation Download or RAM update error occurred.

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

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

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.

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

Action No action required.

PMM-4-ADC_CONV_ERROR: ADC Conversion Failed

Explanation ADC Conversion error happened.

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

PMM-4-ADC_ERROR: ADC Error

Explanation ADC related error happened.

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

PMM-4-ADC_MIDCAL_ERR: ADC MidVoltage calculation error

Explanation ADC MidVoltage calculation error.

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

Queue Engine (QE) Messages

This section contains the Queue Engine (QE) messages.

QE-4-FAIL2REFRESH: QE Initialization Error: qeInitConfigReg

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

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

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

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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

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

RCMP-7-GEN_ERR: [chars]

Explanation General Error.

Action No action required.

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

Explanation Error while adding connections.

Action No action required.

RCMP-7-SRAM_ERR: [chars]

Explanation Static RAM read/write error occurred.

Action No action required.

Redundancy Module (RED) Messages

This section contains the Redundancy Module (RED) messages.

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

Explanation AC_SEND_MSG_FAILED_ERR

Action No action required.

RED-7-GENERAL: ACRED: General ERROR

Explanation AC_GEN_ERR

Action No action required.

RED-7-INFORM: ACRED: Informational

Explanation AC_INFO_ERR)

Action No action required.

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

Explanation AC_MEM_ERR

Action No action required.

RED-7-TIMEOUT: ACRED: State Time out

Explanation AC_TIME_OUT_ERR

Action No action required.

RED-7-WRONGMSG: ACRED: Wrong Message Received

Explanation AC_WRONG_MSG_ERR

Action No action required.

RED-7-DNLDERR: ACRED: Download BRAM Failed

Explanation AC_DWNL_BRAM_ERR

Action No action required.

RED-7-UPLDERR: ACRED: Upload BRAM Failed

Explanation AC_UPLD_BRAM_ERR

Action No action required.

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

Explanation Message error. Data Errors and Unknown Msgs.

Action No action required.

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

Explanation Auto Card send message failed error.

Action No action required.

RED-7-AC_GEN_ERR: General ERROR [chars]

Explanation Auto Card PMM related failure / BRAM related failure.

Action No action required.

RED-7-AC_INFO_ERR: Error Event [chars]

Explanation Autocard error event.

Action No action required.

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

Explanation Auto Card memory error.

Action No action required.

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

Explanation Auto Card time out error.

Action No action required.

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

Explanation Auto Card wrong message type error.

Action No action required.

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

Explanation BRAM download error.

Action No action required.

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

Explanation BRAM upload error.

Action No action required.

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

Explanation Service Module received a bad configuration file.

Action No action required.

RED-7-SMM_ERROR_GEN: General Error [chars]

Explanation General system error.

Action No action required.

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

Explanation System Information.

Action No action required.

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

Explanation SMM bad shelf slot.

Action No action required.

Remote File System (RFS) Messages

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

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

Explanation Unable to get buffer for communication.

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

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

Explanation Unable to create port for communication.

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

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

Explanation Unable to spawn task.

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

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

Explanation Unknown message received.

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

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

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

Explanation RFS request dropped.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

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

Explanation Error in receiving message.

Action No action required.

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

Explanation SPI path addition failed.

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

SCM-4-INIT: psmScmInit failed

Explanation SCM initialization failed.

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

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

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

Explanation SCM SSI message send to application failed.

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

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

Explanation Frame bigger than the expected size received.

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

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

Explanation Unknown cardInx value.

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

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

Explanation Unknown frame received.

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

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

Explanation Card is in the wrong state.

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

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

Explanation NULL pointer encountered.

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

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

Explanation SCM queue overflow.

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

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

Explanation Retransmit queue is empty.

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

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

Explanation Destination not present.

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

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

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

Explanation SSI frame buffer allocation function returned error.

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

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

Explanation Error in receiving SAR buffer.

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

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

Explanation Frame transmission error.

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

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

SCM-7-DEBUG: &msgEventScmDebug[0]

Explanation Debug event.

Action No action required.

Selftest Module (SLFT) Messages

This section contains the Selftest Module (SLFT) messages.

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

Explanation Selftest of the card failed.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The specified function call failed. It failed with the specified return code. A stack trace was generated.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The specified function call failed. It failed with the specified return code.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

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

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

Explanation A call to allocate more memory has failed.

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

SNMP-4-OPENTRANSFAIL: OpenTransport failed.

Explanation An attempt to open the IP layer transport failed.

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

SNMP-4-BINDTRANSFAIL: BindTransport failed.

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

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

SNMP-4-RCVFRTRNSFAIL: ReceiveFromTransport failed.

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

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

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

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

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

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

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

Explanation Invocation of a function using an invalid SRM slot.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An attempt to generate a trap resulted in an error. The card type of the originating slot could not be identified.

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

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

Explanation An invalid varbind was detected during processing.

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

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

Explanation An attempt to create the control point semaphore failed.

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

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

Explanation An attempt to take the control point semaphore failed.

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

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

Explanation An attempt to give the control point semaphore failed.

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

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

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

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

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

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

Explanation An attempted trap generation was disallowed.

Action No action required.

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

Explanation An attempted trap generation was disallowed.

Action No action required.

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

Explanation The RTM trap log buffer has wrapped around.

Action No action required.

Action ical support representative and provide the representative with the gathered information.

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

Explanation An attempt to open an IPC port failed.

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

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

Explanation A call to process_dequeue() failed.

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

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

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

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

Explanation A call to ipc_get_pak_message() has failed.

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

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

Explanation A call to ipc_send_message() has failed.

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

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

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

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

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

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

Explanation SNMP Disk DB initialization failed.

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.

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

failed.

Explanation SNMP Disk Table registration failed.

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.

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

Explanation SNMP RAM DB initialization failed.

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

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

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

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

Explanation Standby RAM update failed. Invalid action requested.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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-DISKDBREADFAIL: [chars] : Disk DB Read failed.

Explanation Explanation SNMP Disk DB Read failed.

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

SNMP-4-DISKDBUPDTFAIL: [chars] : Disk DB Update for elt [dec]

failed. Status [dec].

Explanation SNMP Disk DB Update failed.

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

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.

Action No action required.

SNMP-5-TRAP_DROPPED: Could not generate SNMP trap due to lack of buffers.

Explanation An SNMP trap was dropped due to inadequate resources.

Action No action required.

SNMP-5-TRAPBADSTATE: Could not generate SNMP trap because the PXM state was
invalid.

SNMP-4-UNKNOWNMSG: Unknown message received by [chars] from source [dec]

Explanation A message was received from an unexpected source.

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

SNMP-4-CLONETRAPERR: [chars]

Explanation API Error. Error in cloning an SNMP trap.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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

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

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

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

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

SPI-4-SDRV_ERR: Switch Driver Error : error-id [dec]

Explanation SDRV error.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

SPM-7-SHELFDB_INIT: Shelf Archive file header init failed [chars]

Explanation Failed to initialize shelf archive file header.

Action No action required.

SPM-7-SPM_SMDB_INIT: Slot [dec] Mib [dec] Archive Init Failed [chars]

Explanation Failed to initialize slot archive file.

Action No action required.

SPM-4-SPM_EPTDB_BAD: SPM database corrupt [chars]

Explanation SPM database corruption.

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

SPM-7-RM_RAMDB_INIT: Resource Mgr Ram DB init failed [chars]

Explanation Failed to initialize Resource RAM Database.

Action No action required.

SPM-7-SPM_TIMER_ERROR: Timer operation error [chars]

Explanation Failed to start the timer.

Action No action required.

SPM-7-SPM_MEM_ERROR: Memory allocation error [chars]

Explanation Failed to allocate memory.

Action No action required.

SPM-7-SPM_MSG_ERROR: Message send failed [chars]

Explanation Failed to send message.

Action No action required.

SPM-7-SPM_ERR_GEN: [chars]

Explanation General error.

Action No action required.

SPM-4-RM_API_ERROR: [chars] [dec] [dec]

Explanation RM API parameter error.

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

SPM-4-RM_NULL_PTR: EVENT_DUMP_TRACE EVENT_NO_ACTION [chars] is NULL

Explanation NULL pointer in RM API.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to register the SRM TASK data base SRMCT task will not be able to spawn properly.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to read/update data base entry because of invalid table ID SRMCT task will not be able to spawn properly.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to read/update data base entry because of invalid table ID SRMCT task will not be able to spawn properly.

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

SRM-4-SRMCT_INIT_ERR: Init Error: [chars]

Explanation SrmComTask initialization error.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 SRM CARD went in to Mismatch because this hardware revision is not supported in POPEYE

Action No action required.

SRM-7-LEGACY_ERR_RPT: Srbm Error Rpt: [chars]: [chars]

Explanation Srbm error has occurred.

Action No action required.

System Service Interface (SSI) Messages

This section contains the System Service Interface (SSI) messages.

SSI-4-ARCH_ERROR: Archive Error : [chars]

Explanation The archive file doesn't exist on the service module.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 API Software Error. The parameter value for the named parameter passed in as an argument to the named function exceeded maximum value specified.

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

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.

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

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.

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.

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.

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The VxWorks semaphore used to protect the specified system table was not able to be taken. SSI may not be initialized properly.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Creation of a Vxworks object failed due to a memory shortage in the VxWorks system memory partition.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid deadlock action value was passed in as an argument to create an SSI semaphore.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid semaphore type value was passed in as an argument to create an SSI semaphore.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid semaphore option value was passed in as an argument to create an SSI semaphore.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid semaphore initial state value was passed in as an argument to create an SSI semaphore.

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

SSI-4-SEMCREATEFAIL: Semaphore creation failed. Errno=[hex].

Explanation Creation of a semaphore failed unexpectedly.

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

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.

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

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.

Action No action required.

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.

Action No action required.

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.

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

SSI-4-SEMTAKEFAIL: Take of semaphore [dec]ed. Errno=[hex]

Explanation The Take of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly.

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

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.

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

SSI-4-SEMGIVEFAIL: Give of semaphore [dec]ed. Errno=[hex]

Explanation The Give of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly.

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

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.

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

SSI-4-SEMFLUSHFAIL: Flush of semaphore [dec]ed. Errno=[hex]

Explanation The Give of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid maximum number messages in the message queue was passed in as an argument to create an SSI message queue.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid message length value was passed in as an argument to create an SSI message queue.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid owner task id value was passed in as an argument to create an SSI message queue.

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

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.

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

SSI-4-MQCREATEFAIL: Message Queue creation failed. Errno=[hex].

Explanation Creation of a message queue failed unexpectedly.

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

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

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.

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

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.

Explanation An invalid message queue quota value was passed in as an argument to set the quota on a SSI message queue.

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

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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The receive on the VxWorks message queue to flush it failed unexpectedly. It could have been corrupted or deleted unexpectedly

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid message length value was passed in as an argument to send message to an SSI message queue.

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

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.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The send to message queue was done by an Interrupt Service Routine with a non zero timeout value. ISRs cannot block.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid message length value was passed in as an argument to receive message from an SSI message queue.

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

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.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid message handler function pointer value was passed in as an argument to create an SSI message queue that requires a message handler.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The message handler function returned failure while processing a message received in the SSI message queue.

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

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.

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

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.

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

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.

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

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.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The SSI_TID failed to initialize properly and was suspended to prevent further errors.

Action No action required.

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.

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

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.

Action No action required.

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.

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

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.

Action No action required.

SSI-4-TASKRESUMEFAIL: Resume of task [dec]ed. Errno=[hex]

Explanation The resumption of VxWorks task used to implement the SSI_TID failed unexpectedly.

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

SSI-4-TASKSUSPENDFAIL: Suspend of task [dec]ed. Errno=[hex]

Explanation The suspension of VxWorks task used to implement the SSI_TID failed unexpectedly.

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

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.

Explanation An invalid task priority number was passed in as an argument to create an SSI task.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid task priority group was passed in as an argument to create an SSI task.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid task application id value was passed in as an argument to create an SSI task.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid task stack size value was passed in as an argument to create an SSI task.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid task suspend action value was passed in as an argument to create an SSI task.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An invalid task fail action value was passed in as an argument to create an SSI task.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The creation of VxWorks semaphore used to synchronize SSI_TID initialization with parent failed unexpectedly.

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

SSI-4-TASKSPAWNFAIL: Task spawn failed. Errno=[hex].

Explanation Spawning of a task failed unexpectedly.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The parent SSI_TID was unable to wait for the send of initialization status from the child task.

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

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.

Action No action required.

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).

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

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.

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

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.

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

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.

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

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

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

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.

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

SSI-4-ZEROSIZE: A request for 0 bytes was made.

Explanation An attempt was made to allocate 0 bytes. This indicates a software problem.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An attempt was made to allocate more memory than what is allocated for the partition.

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

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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An error was returned by memPartAlloc while attempting to allocate memory.

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

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.

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

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.

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

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.

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

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.

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

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

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

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The memory type stored in the header of the block is wrong. This indicates that the header has been corrupted or is invalid.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The length stored by VxWorks is wrong. This indicates that memory has been corrupted.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The magic number stored at the end of the block is wrong. This indicates that memory has been corrupted.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The reference count for the block is 0. This indicates that the block has already been freed.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The partition index in the header is invalid. This indicates that the header has been corrupted or is invalid.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The chunk memory manager could not create the mutex semaphore necessary for its operation.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The required memory size was not allocated for this pool. This indicates a software problem.

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

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.

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

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.

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

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.

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

SSI-4-CHUNKINVID: The pool ID 0x[hex] is invalid.

Explanation The pool ID is invalid. This indicates a software problem.

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

SSI-4-CHUNKSHORTAGE: The pool 0x[hex] doesn't have a chunk to allocate.

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

SSI-4-CHUNKINVPTR: The chunk pointer is invalid.

Explanation The chunk pointer is invalid. This indicates a software problem.

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

SSI-4-CHUNKNOTALLOC: The chunk 0x[hex] is not allocated.

Explanation The chunk is not allocated. This indicates a software problem.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The magic number stored at the end of the block is wrong. This indicates that memory has been corrupted.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An attempt to create a Vx POSIX timer failed. SSI timers may not be initialized properly.

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

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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An SSI function was called with an invalid timer ID. SSI timers may not be initialized properly.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An SSI function was called for an invalid timer entry. SSI timers may not be initialized properly.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 An SSI function was called to operate on a timer entry by a non-owning task. SSI timers may not be initialized properly.

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

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.

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

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.

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

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.

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

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.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 The function call to putenv to put a variable into the environment failed with the error code specified.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to create the specified watchdog for the specified use in the named function. It failed with the specified error number.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 Unable to start the specified watchdog for the specified use in the named function. It failed with the specified return code and error number.

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

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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

SYS-7-STARTUP: System is up and the Reset Reason is: [[chars]]

Explanation System started after reset.

Action No action required.

SYS-7-VERSION: Boot Code Rev: [[chars]] FW Rev: [[chars]]

Explanation Version of Backup Boot and runtime FW image.

Action No action required.

SYS-2-TASKINITFAIL: Task[[chars]] failed of spawning

Explanation Failed to spawn task.

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.

SYS-1-TASKHOLDCPU: Task[[chars]] is holding CPU

Explanation System has detected a ready task.

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.

SYS-1-NOTASKHOLDCPU: unknown Task is holding CPU

Explanation System has detected a task that is ready but not using the CPU.

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.

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.

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.

SYS-1-BKTASKSUSPEND: Background Task is suspended and could not restart

Explanation The Background Task is suspended, and could not restart.

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.

SYS-6-BKTASKRESTART: Background Task is suspended and restart is successful

Explanation The Background Task got suspended, and restart is successful.

Action No action required.

SYS-1-TASKLOSTFATAL: Trouble-Task[[chars]]: action is SYSTEM RESET

Explanation A task has disappeared or suspended, and could cause system RESET.

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.

SYS-3-TASKLOST: Trouble-Task[[chars]]: action is [chars]

Explanation A task has disappeared or suspended.

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.

SYS-2-RECVTASKFAIL: Failed to [chars] Task[[chars]]

Explanation A task has disappeared or suspended, and SYSTEM is not RESET

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.

SYS-3-WRONGTYPTKRECV: Wrong Type[[dec]] to recv task[[chars]}

Explanation taskRecover(): wrong type to recover a task.

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.

SYS-1-FILEOPENFAIL: failed to open event log file

Explanation Failed to open event log file.

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.

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.

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.

Explanation The message received by the specified function as a parameter is invalid. The message size and contents are specified.

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 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.

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.

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.

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.

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.

Action No action required.

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.

Action No action required.

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.

Trivial File Transfer Protocol (TFTP) Messages

Explanation Received error while trying to read data from TFTP socket.

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

Action Copy the error message exactly as it appears in the system log. Issue the dsperr command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.

VCNM-4-INIT_FAIL: VCNM : pipc port create failed : err [dec]

Explanation Initialization failure.

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

Virtual Switch Interface (VSI) Messages

This section contains the Virtual Switch Interface (VSI) messages.

VSI-4-VSI_MSG_LENGTH: VSI_MSG_LENGTH: [chars]

Explanation VSI msg length problem.

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

VSI-4-VSI_PG_LENGTH: VSI_PG_LENGTH: functionCode[hex] pgFmtId[hex]

Explanation VSI pg length problem.

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

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

VSI-4-VSI_CONTROLLER: VSI_CONTROLLER: [chars]

Explanation VSI Controller Problem.

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

VSI-4-VSI_SAP: VSI_SAP: [chars]

Explanation VSI SAP problem.

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

VSI-4-VSI_MSGQ: VSI_MSGQ: [chars]

Explanation VSI msg queue problem.

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

VSI-4-VSI_SOCKET: VSI_SOCKET: [chars]

Explanation VSI socket problem.

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

VSI-4-VSI_UNKNOWN_CMD: VSI_UNKNOWN_CMD: [hex]

Explanation Unknown VSI command.

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

VSI-4-VSIS_TRAP: VSIS_TRAP: [chars] [dec]

Explanation VSI Slave trap problem.

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

VSI-7-VSIS_TX: VSIS_TX: [chars]

Explanation VSI Slave transport problem.

Action No action required.

VSI-7-NULL_PTR: NULL_PTR at [chars]

Explanation NULL pointer

Action No action required.

VSI-4-MALLOC_FAIL: MALLOC_FAIL

Explanation ssiMalloc() failed.

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

VSI-4-FREE_FAIL: FREE_FAIL

Explanation ssiFree() failed.

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

VSI-4-FBALLOC_FAIL: MALLOC_FAIL

Explanation ssiFrameBufferAlloc() failed.

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

VSI-4-FBFREE_FAIL: FREE_FAIL

Explanation ssiFrameBufferFree() failed.

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

VSI-4-VSI_TIMER: VSI_TIMER: [chars]

Explanation VSI timer problem.

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

VSI-4-VSI_CLK: VSI_CLK: [chars]

Explanation VSI clock source problem.

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

VSI-7-SSI_VSI_IF: SSI_VSI_IF: [chars]

Explanation SSI VSI IF problem.

Action No action required.

Virtual Service Module (VSM) Messages

This section contains the Virtual Service Module (VSM) messages.

VSM-4-DISK_UPD_FAIL: VSM : [chars] : PXM Disk Update Failed

Explanation Disk update failed.

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

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

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

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