MGX and SES Error Messages, Release 4
MGX and SES Error Messages, Release 4 (part A4)
-
MGX and SES Error Messages, Release 4
-
Preface to MGX and SES Error Messages, Release 4
-
MGX and SES Error Messages, Release 4 (part A1)
-
MGX and SES Error Messages, Release 4 (part A2)
-
MGX and SES Error Messages, Release 4 (part A3)
-
MGX and SES Error Messages, Release 4 (part A4)
-
MGX and SES Error Messages, Release 4 (part B1)
-
MGX and SES Error Messages, Release 4 (part B2)
-
MGX and SES Error Messages, Release 4 (part B3)
-
MGX and SES Error Messages, Release 4 (part B4)
-
MGX and SES Error Messages, Release 4 (part C1)
-
MGX and SES Error Messages, Release 4 (part C2)
-
MGX and SES Error Messages, Release 4 (part C3)
-
MGX and SES Error Messages, Release 4 (part C4)
-
MGX and SES Error Messages, Release 4.0.10 (part D)
-
Download this chapter
Download the complete book
Feedback
Table Of Contents
DDTS "control-point/pxm-connmgm"
DB2S-5-DBSYNC_INVROLE
SEVERITY: WarningFORMAT: "%s Should be called on %s, current role is 0x%x."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The function is expected to be called only on Active card. It is called on the card with specified role."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_INVSTATE
SEVERITY: WarningFORMAT: "%s Can't be called when Server status is 0x%x."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The function is NOT expected to be called when DB Server is in the given state."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_INVFWDIR
SEVERITY: WarningFORMAT: "%s Invalid FW Path configured. Expected=%s, configured=%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid path is configured as the first entry in the NON-DB Directory table for FW Path."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_INVTX
SEVERITY: WarningFORMAT: "%s Invalid Tx Table Index, got %d, should be less than %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync task got a File Replication response with invalid Tx Table index."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-DBSYNC_DUPLRESP
SEVERITY: InformationFORMAT: "%s Duplicate File Replication Response received, Id=%d, Type=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync task received a duplicate response to a file replication request."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-2-DBSYNC_REPL_FAI
SEVERITY: Major AlertFORMAT: "%s Failed to %s %s to/on the Standby."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The DB Manager Sync module failed to copy/rename/delete given file on the Standby PXM. This could be due to lack of IPC buffers either on Active controller card or Standby controller card. This error could also occur due to failure to access disk either on Standby or on Active controller card. This results in Standby controller card getting out of sync with the Active controller card. Note that this is not considered loss of core redundancy."RECOMMENDED ACTION: "Don't attempt to switchover untill the importance of the file operation that didn't get replicated is evaluated. Call TAC."REQUIRED INFO: "Take hot dump on both Active and Standby controller cards. Collect event and error logs."DB2S-4-DBSYNC_EPHNDLR
SEVERITY: ErrorFORMAT: "Error 0x%x in attaching the msg handler to DBSYNC epid 0x%x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The DB Manager sync module failed to attach handler function to one of the message queues. This could be due to either bad image or bad hardware. If this error occurs, the card doesn't come up."RECOMMENDED ACTION: "Try resetting the card one more time. If this error persists, try replacing the card. If this error still persists, call TAC."REQUIRED INFO: "Save the core. Collect event and error logs."DB2S-5-DBSYNC_MEM_FAIL
SEVERITY: WarningFORMAT: "%sError 0x%x on %s 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync encoutered failure when called an SSI MEMORY API function."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_TXALLOC
SEVERITY: WarningFORMAT: "%s Failed to allocate Tx Table Entry"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync encoutered failure when tried to allocate Async Tx Table entry"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_IPC_FAIL
SEVERITY: WarningFORMAT: "%sError 0x%x %s 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync encountered failure when called an SSI IPC API function."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-3-DBSYNC_DOS_FAIL
SEVERITY: Minor AlertFORMAT: "%sError 0x%x in %s %d, %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The DB Manager Sync module encoutered failure while accessing the hard disk. This could be due to memory corruption or internal error or bad hard disk. If this error occurs while Standby controller card is coming up, it fails to come up. If this error occurs while replicating a file, the file replication operation fails."RECOMMENDED ACTION: "If this error occured on the Standby controller card while it is coming up, reset the Standby controller card one more time. It the problem still persists and is on the Standby controller card, change the Standby hard disk card. If the problem still persists, call TAC."REQUIRED INFO: "Save core dump. Collect event and error logs."DB2S-3-DBSYNC_DOS_SZ_E
SEVERITY: Minor AlertFORMAT: "%s Actual file size on Active = %d bytes, Copied %d bytes."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The actual number of bytes read from Active controller card doesn't match with the actual size of the file received from Active controller card. This error occurs on the Standby controller card. This could be due to the specified file getting cross linked to another file on the disk. This error could also occur if there is a buffer corruption. This error leads to failure of the file replication operation or disk synchronization while Standby controller is coming up."RECOMMENDED ACTION: "Remove the file in error on Active controller card and transfer file onto the hard disk. If this error occured while Standby controller card was coming up, reset the Standby controller card. If this error still persists, call TAC."REQUIRED INFO: "Collect event and error logs."DB2S-5-DBSYNC_RMT_CPY
SEVERITY: WarningFORMAT: "%s Copying %s from Active failed. Check the file on ACTIVE."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Remote file copy during File Sync has failed. The actual number of bytes read doesn't match with the actual size of the file received from Active."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-3-DBSYNC_DOS_RENA
SEVERITY: Minor AlertFORMAT: "%sError 0x%x in %s %s to %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The DB Manager Sync module failed to rename or copy a file. This error could be due to lack of disk space, file system or hard disk failure. This results in failing the file replication operation on the Standby controller card."RECOMMENDED ACTION: "Change the directory to the path specified in the event and check the available disk space using 'll' command. If it is due to lack of disk space, clean up the disk and reissue the operation that initiated the replication (say, transfering the file to Active controller card or renaming a file in one of the replicated directories etc). If the error is not due to lack of disk space, try changing the Standby controller hard disk."REQUIRED INFO: "Collect event and error logs."DB2S-5-DBSYNC_DOS_REMO
SEVERITY: WarningFORMAT: "%sError 0x%x in %s %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The DB Manager Sync module failed to remove a file. This error could be due to file system or hard disk failure. This results in failing the file replication operation on the Standby controller card."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_RECVMSG
SEVERITY: WarningFORMAT: "Error 0x%x receiving IPC message on DB Sync Port"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync task failed to receive IPC message"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_ACTNACK
SEVERITY: WarningFORMAT: "NACK received from Active Server for %s, reason=0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync task on Standby received a NACK from for the specified request."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_STBNACK
SEVERITY: WarningFORMAT: "%s NACK received from Standby Server for %d, reason=0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync task or app on Active received a NACK from for the specified request."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_INVNACK
SEVERITY: WarningFORMAT: "%s Invalid NACK received for %d, reason=0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync task or app received a NACK with invalid request type."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_GEN_FAIL
SEVERITY: WarningFORMAT: "%s%s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync encountered a general failure while processing the request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_GEN_FAIL
SEVERITY: WarningFORMAT: "%s. Extra Info- %s<0x%x>"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync detected general failure condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_GEN_FAIL
SEVERITY: WarningFORMAT: "%s. Extra Info- %s<0x%x> %s<0x%x>"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync detected general failure condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_GEN_FAIL
SEVERITY: WarningFORMAT: "%s. Extra Info- %s<0x%x> %s<0x%x> %s<0x%x>"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync detected general failure condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_VER_NOTS
SEVERITY: WarningFORMAT: "Message version %x not supported. Current version is %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync task received an interface message of which the version is incompatible with the version that the DB Server task is running"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_RETXFAIL
SEVERITY: WarningFORMAT: "%s Error 0x%x on %s epid = %d, &queue = 0x%x, data %s = %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync encoutered failure when called an SSI REXMIT api"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-DBSYNC_BAD_SWID
SEVERITY: InformationFORMAT: "%s SW Id mismatched on slot <%d>, Expected[%d.%d.%d.%d], Received[%d.%d.%d.%d]"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Server detected mismatch on the SW Version received from DB Client's message."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-UNK_SWID
SEVERITY: WarningFORMAT: "%s Lslot=%d, Prim=%d.%d.%d.%d.%d Sec=%d.%d.%d.%d.%d Given=%d.%d.%d.%d.%d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync failed to find the control block for the specified logical slot and given software version as neither the primary or the secondary software version matches with the given software version."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-3-DBSYNC_MAX_TRIE
SEVERITY: Minor AlertFORMAT: "%s Failed to sync one or more UNSTABLE logical slots"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The DB Manager Sync module has failed to sync the configuration of one or more of the slots. This error occurs when one or more Service Module don't go Active READY, but, are stuck in boot/init state. If a Service Module is stuck in boot/init state, that slot is considered unstable and the Standby controller card skips that slot and continues with the rest while coming up. The Standby controller card attempts to sync a given slot an arbitrary number of times and if the card continues to be unstable, the Standby controller card fails to complete the disk sync. This results in Standby controller card failing to come up."RECOMMENDED ACTION: "Using the command to display the status of the cards in the node, determine the slots in which the Service Modules are attempting to come up as Active, but are stuck in boot/init state. Remove those cards from the node and reset the Standby controller card."REQUIRED INFO: "Collect the event and error logs to determine why the Service Module(s) are stuck in boot/init state."DB2S-5-SYNCFAIL
SEVERITY: WarningFORMAT: "%s Failed to sync the old version for lslot %d, sync errno 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync failed to sync the old version Db directories for the specified logical slot beacuse of the error specified by the sync errno."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-SYNCMAXRETRY
SEVERITY: WarningFORMAT: "%s Failed to sync %s version for lslot %d, no tries (%d) > max (%d)"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync failed to sync the old version Db directories for the specified logical slot beacuse the number of attempts exceeded the specified maximum."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-INVREPDIR
SEVERITY: WarningFORMAT: "Replicated directory %s contains a subdirectory %s. %s is not sync'ed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync doesn't not sync specified subdirectory in the specified replicated directory."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_OS_FAIL
SEVERITY: WarningFORMAT: "%sError 0x%x %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync encountered failure when called an SSI-OS function."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_INTERNAL
SEVERITY: WarningFORMAT: "%sInternal failure - %s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync detected internal data structure inconsistency"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_INTERNAL
SEVERITY: WarningFORMAT: "%sInternal failure - Error 0x%x while %s."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync detected internal data structure inconsistency"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_WARNING
SEVERITY: WarningFORMAT: "%s%s %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync detected a warning condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_WARNING1
SEVERITY: WarningFORMAT: "%s%s %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Sync detected a warning condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-4-DBSYNC_BAD_DATA
SEVERITY: ErrorFORMAT: "DBSYNC bad data in %s Bad data 0x%x, 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The DB Manager Sync module has detected invalid values in its data structures. This could be due to memory corruption. This results in failing the disk synchronization. As a result, the Standby controller card doesn't come up."RECOMMENDED ACTION: "Try resetting the card. If the error still persists, try replacing the card."REQUIRED INFO: "Save core dump. Collect event and error logs."DB2S-5-DBSYNC_SEM_FAIL
SEVERITY: WarningFORMAT: "DBSYNC function %s errno = 0x%x while %s 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DbSync failed to create semaphore"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-SLOTABORT
SEVERITY: InformationFORMAT: "DBSYNC Aborted syncing of lslot %d. Reason %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Syncing of the specified slot has been aborted for the specified reason"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-SYNCBE
SEVERITY: InformationFORMAT: "The Standby PXM %s %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Db Sync started/completed (as specified) the specified Sync (DB/Non-DB/Old Version)."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-FULLSYNC
SEVERITY: InformationFORMAT: "The Standby PXM is going to perform a full DB sync for one or more slots"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Db Sync detected that the Standby PXM doesn't have anything for one or more slots and needs to sync everything for those slots from Active PXM."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-SYNCDONE
SEVERITY: InformationFORMAT: "%s%dSending SYNC_DONE Req for Lslot %d Version %d.%d.%d.%d Card State %d Reason%s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Standby DB Sync is sending SYNC_DONE request to Active for the specified logical slot, software version, card state and the reason."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-RSTCNFSUC
SEVERITY: InformationFORMAT: "The configuration successfully restored from %s on STANDBY"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Db Sync successfully restored the configuration from the specified configuration file on the Standby PXM."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-RSTCNFFAIL
SEVERITY: WarningFORMAT: "Failed to perform restoreallcnf from %s on STANDBY"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Db Sync failed to restore the configuration from the specified configuration file on the Standby PXM. The reason would have been logged prior to this event."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-UNZIPFAIL
SEVERITY: WarningFORMAT: "Failed to unzip %s, errno=0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Db Sync failed to unzip the specified zip file while restoring the configuration on Standby PXM."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-NODB
SEVERITY: InformationFORMAT: "%s No DBs for lslot=%d swId=%d.%d.%d.%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Db Sync on the Active PXM didn't find the DBs for the specified logical slot and swVersion. The DB directory corresponding to this logical slot and the s/w version will be deleted on the Standby."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-EMPLSLOT
SEVERITY: InformationFORMAT: "%s No DB version directories for lslot=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Db Sync on the Standby PXM didn't find any DBs for this logical slot. So, it deletes the directory corresponding to this logical slot."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-DBSYNC_UNEXPEVT
SEVERITY: WarningFORMAT: "Unexpected %s 0x%x. %s %d, %s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Sync task Received CTC events that belongs to other logical slot which the server did not register for."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-6-IGNUPDCNT
SEVERITY: NoticeFORMAT: "Dropped Update Counter (%d) for lslot=%d, swId=%d.%d.%d.%d"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Db Sync on the Standby PXM dropped the update counters received for specified logical slot and software version because it could not find the slot running that software version."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-4-UNEXPRESP
SEVERITY: ErrorFORMAT: "Received unexpected response. Expected type = %d, received type = %d"FLAG: Write to BramTHROTTLING: No ThrottlingEXPLANATION: "The DB Manager Sync module on Standby contoller card has received a response message for which it is not waiting for from the Active controller card. This could happen when the Active controller card responded to certain requests from Standby controller card after the Standby controller card has timed out waiting for the response and waiting for the response for the next request. This error results in Standby controller card failing to complete the disk synchronization. When this happens, the card gets reset and in most casesit will complete the synchronization in the next attempt."RECOMMENDED ACTION: "In most cases, it may be intermittent and doesn't persist. But, if it persists, the Standby controller card will be eventually put in FAILED state. If this happens, call TAC."REQUIRED INFO: "Save the core dump on the Active controller card and Standby controller card. Collect the event and error logs."DB2S-7-CNFCREATEREQ
SEVERITY: InformationFORMAT: "%s %s 0x%x"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "DbSync's config create request sending /receiving."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-7-CNFCREATERESP
SEVERITY: InformationFORMAT: "%s %s %s, %d, %d"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "DbSync's config create response sending/receiving."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-CNFZIPFAIL
SEVERITY: WarningFORMAT: "Create config zip - %s 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Active Db Sync failed to zip the specified zip file due to incomplete zip, fail zip, fail stat file or fail to response."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-5-REGFORCEFALSE
SEVERITY: WarningFORMAT: "Reg in progress forced FALSE. LSlot=%d"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "The Active DB Server forced the registration status for the specified slot to be FALSE so as to allow Standby DB Server sync'ing the specified slot after the Standby DB Server exhausted maximum number of attempts while waiting for the DB registration for the slot to be completed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2S-4-REGFORCEDONE
SEVERITY: ErrorFORMAT: "Reg status forced DONE. LSlot=%d, SwId=%d.%d.%d.%d"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "The Active DB Server forced the registration status for the specified slot/version to be DONE so as to allow Standby DB Server sync'ing the specified slot/version after the Standby DB Server exhausted maximum number of attempts while waiting for the DB registration for the slot/version to be completed. This may result in both Active and Standby DB Server having incomplete DB registration information."RECOMMENDED ACTION: "Call TAC"REQUIRED INFO: "Collect event logs and hot-core-dump."DDTS "diskdb"
DB2V-4-DBVERF_TMRERR
SEVERITY: ErrorFORMAT: "%s Error 0x%x creating Sync Timer for File Repl Retx."FLAG: Write to BramTHROTTLING: One TickEXPLANATION: "The DB Manager Verify module has failed to create a timer. This could be due to memory shortage or leakage. If this error occurs, the card will not come up."RECOMMENDED ACTION: "Reset the card one more time and see if it comes up. If the problem persists, try with another controller card."REQUIRED INFO: "Collect and save the core, event logs and error logs."DB2V-5-DBVERF_CTCAPI
SEVERITY: WarningFORMAT: "Error 0x%x on call to %s"FLAG: Write to BramTHROTTLING: One TickEXPLANATION: "DB Verify task failed on querying the CTC using the CTC API functions"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-4-DBVERF_SHMAPI
SEVERITY: ErrorFORMAT: "Error 0x%x on call to %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The DB Manager Verify module failed to get required information for the Shelf Manager Module. This could be due to lack of IPC buffers or internal error. If this error occurs, regardless of whether it occured on Active controller card or Standby controller card, the Standby controller card doesn't come up."RECOMMENDED ACTION: "Call TAC"REQUIRED INFO: "Take hot dump and collect event and error logs."DB2V-4-DBVERF_DATAXFER
SEVERITY: ErrorFORMAT: "%s Error 0x%x on call to %s"FLAG: Stack Trace|Write to BramTHROTTLING: One TickEXPLANATION: "The DB Manager Verify module failed while using Data Transfer services. This could be due to internal error. This results in Standby controller card failing to come up."RECOMMENDED ACTION: "Reset the Standby controller card. If this error still persists, call TAC."REQUIRED INFO: "Take hot dump of both the Active and Standby controller cards. Collect event and error logs."DB2V-5-DBVERF_INVMSGTY
SEVERITY: WarningFORMAT: "%s Message received with Invalid Type = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify task received a message with invalid message type."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_INVMSGLG
SEVERITY: WarningFORMAT: "%s Invalid Message Length Lg in Hdr %d should be <= %d+%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify task received a message with invalid message Length. The length in header should be less than or equal to the Msg Len given by the IPC + message header size."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_HDRVAL
SEVERITY: WarningFORMAT: "Header Validation Invalid %s-expected 0x%x LSlot 0x%x MsgType 0x%x MsgLen 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify task received a message with invalid header contents."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_HDRVALMM
SEVERITY: WarningFORMAT: "Header Validation Invalid %s-expected [0x%x-0x%x] LSlot 0x%x MsgType 0x%x MsgLen 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify task received a message with invalid header contents."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_INVRESPI
SEVERITY: WarningFORMAT: "%s Invalid File Response, expected = 0x%x or 0x%x, received 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Application/DB Verify task received an invalid response to File Replication request."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_LENVAL
SEVERITY: WarningFORMAT: "%s Invalid message length, expected >= %d, received %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify task received a message with invalid message length."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_INVVAL
SEVERITY: WarningFORMAT: "%s Invalid %s, expected >= %d, received %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verf task received a message with invalid value for the specified field."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_INVLVAL
SEVERITY: WarningFORMAT: "%s Invalid %s, expected <= %d, received %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Verify task received an invalid value for the specified field."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_INSUF_BU
SEVERITY: WarningFORMAT: "%s Insufficient buffer SendLen=%d, Need %d more, Total Avail=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verf task preparing a response message and the buffer that has been allocated is insufficient."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_MEM_FAIL
SEVERITY: WarningFORMAT: "%sError 0x%x on %s 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify encoutered failure when called an SSI MEMORY API function."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_IPC_FAIL
SEVERITY: WarningFORMAT: "%sError 0x%x %s 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify encountered failure when called an SSI IPC API function."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_RECVMSG
SEVERITY: WarningFORMAT: "Error 0x%x receiving IPC message on DB Verf Port"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify task failed to receive IPC message"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_GEN_FAIL
SEVERITY: WarningFORMAT: "%s%s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Verify encountered a general failure while processing the request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_GEN_FAIL
SEVERITY: WarningFORMAT: "%s. Extra Info- %s<0x%x>"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Verify detected general failure condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-7-DBVERF_BAD_SWID
SEVERITY: InformationFORMAT: "%s SW Id mismatched on slot <%d>, Expected[%d.%d.%d.%d], Received[%d.%d.%d.%d]"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Server detected mismatch on the SW Version received from DB Client's message."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-UNK_SWID
SEVERITY: WarningFORMAT: "%s Lslot=%d, Prim=%d.%d.%d.%d.%d Sec=%d.%d.%d.%d.%d Given=%d.%d.%d.%d.%d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Verify failed to find the control block for the specified logical slot and given software version as neither the primary or the secondary software version matches with the given software version."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_OS_FAIL
SEVERITY: WarningFORMAT: "%sError 0x%x %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verify encountered failure when called an SSI-OS function."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_INTERNAL
SEVERITY: WarningFORMAT: "%sInternal failure - %s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verf detected internal data structure inconsistency"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_INTERNAL
SEVERITY: WarningFORMAT: "%sInternal failure - Error 0x%x while %s."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Verf detected internal data structure inconsistency"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_WARNING
SEVERITY: WarningFORMAT: "%s%s %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Verify detected a warning condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_WARNING1
SEVERITY: WarningFORMAT: "%s%s %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "DB Verify detected a warning condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-4-DBVERF_BAD_DATA
SEVERITY: ErrorFORMAT: "DBVERF bad data in %s Bad data 0x%x, 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The DB Manager Verify module has detected invalid values in its data structures. This could be due to memory corruption."RECOMMENDED ACTION: "Try resetting the card. If the error still persists, try replacing the card."REQUIRED INFO: "Save core dump. Collect event and error logs."DB2V-5-DBVERF_SEM_FAIL
SEVERITY: WarningFORMAT: "DBVERF function %s errno = 0x%x while %s 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DbVerf failed to create semaphore"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-7-SLOTABORT
SEVERITY: InformationFORMAT: "DBVERF Aborted DiskVerf of lslot %d. Reason %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Verifying of the specified slot has been aborted for the specified reason"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-7-VERFDONE
SEVERITY: InformationFORMAT: "%s%dSending SYNC_DONE Req for Lslot %d Version %d.%d.%d.%d Card State %d Reason%s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Standby DB Verify is sending VERF_DONE request to Active for the specified logical slot, software version, card state and the reason."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-5-DBVERF_UNEXPEVT
SEVERITY: WarningFORMAT: "Unexpected %s 0x%x. %s %d, %s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB Verf task Received CTC events that belongs to other logical slot which the server did not register for."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDB2V-4-UNEXPRESP
SEVERITY: ErrorFORMAT: "Received unexpected response. Expected type = %d, received type = %d"FLAG: Write to BramTHROTTLING: No ThrottlingEXPLANATION: "The DB Manager Verify module on Standby contoller card has received a response message for which it is not waiting for from the Active controller card. This could happen when the Active controller card responded to certain requests from Standby controller card after the Standby controller card has timed out waiting for the response and waiting for the response for the next request. This error results in Standby controller card failing to complete the disk verification."RECOMMENDED ACTION: "In most cases, it may be intermittent and doesn't persist. If it persists, call TAC."REQUIRED INFO: "Save the core dump on the Active controller card and Standby controller card. Collect the event and error logs."DB2V-4-DBVERF_TASKUNSA
SEVERITY: ErrorFORMAT: "A call to ssiTaskUnsafe for Task 0x%x failed."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "A call to ssiTaskUnsafe failed while attempting to unlock a resource. This task cannot currently be deleted."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoDB2V-3-DBVERF_DOS_FAIL
SEVERITY: Minor AlertFORMAT: "%sError 0x%x in %s %d, %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The DB Manager Verf module encoutered failure while accessing the hard disk. This could be due to memory corruption or internal error or bad hard disk."RECOMMENDED ACTION: "Reset the Standby controller card. It the problem still persists and is on the Standby controller card, change the Standby hard disk card. If the problem still persists, call TAC."REQUIRED INFO: "Save core dump. Collect event and error logs."DDTS "snmp-ma"
SNMP-4-SNMP_ERR
SEVERITY: ErrorFORMAT: "SNMP Agent Error %s at line %d in file %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This error is logged as a result of errors in SNMP master-agent"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.DDTS "axsme-apps"
APS-6-ADD_LN
SEVERITY: NoticeFORMAT: "APS Line Redundancy added with Work Line = %d.%d.%d, Prot Line = %d.%d.%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Added.The event log would show the working and protection line indices. "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-DEL_LN
SEVERITY: NoticeFORMAT: "APS Line Redundancy deleted with Work Line = %d.%d.%d , Prot Line = %d.%d.%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Pair deleted"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-CNF_SFBER
SEVERITY: NoticeFORMAT: "Aps Line Reconfigured. SF BER changed %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "SF Ber changed by user"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-CNF_SDBER
SEVERITY: NoticeFORMAT: "Aps Line Reconfigured. SD BER changed %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "SD Ber changed by user."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-CNF_WTR
SEVERITY: NoticeFORMAT: "Aps Line Reconfigured. WTR changed %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Wait To Restore time limit changed by user This indicates the time the selector will continue to select traffic from the protection line even after the fault condition in the working line is repaired/removed before switching back to the working line"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-CNF_DIR
SEVERITY: NoticeFORMAT: "Aps Line Reconfigured. Direction changed %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Directionality (Uni/Bi) is changed by user. The event is logged only when there is a change in the direction."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-CNF_REV
SEVERITY: NoticeFORMAT: "Aps Line Reconfigured. Revertive changed %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Revertive mode changed by user The event is logged only when there is change in the mode."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-CNF_PROTOCOL
SEVERITY: NoticeFORMAT: "Aps Line Reconfigured. APS Protocol(Bellcore/ITU) changed %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "APS Protocol(Bellcore/ITU) changed by user. If ITU Protocol is configured then directionality info (UNI/BI) in K2 byte will not be indicated"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SF_DECL
SEVERITY: Minor AlertFORMAT: "APS Signal Fail Error (LOS/LOF/AIS-L) on %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "APS Signal Fail condition detected due to LOS/LOF/AIS-L on the line."RECOMMENDED ACTION: "Check the line cable on local end and remote end. Check the backcard status on local end and remote end."REQUIRED INFO: No action required. Operational event log only.APS-3-SF_DECL_CLEAR
SEVERITY: Minor AlertFORMAT: "APS Signal Fail Error (LOS/LOF/AIS-L) Cleared on %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Aps Signal Fail alarm condition cleared. Logging the event for informational purpose."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SF_BER_DECL
SEVERITY: Minor AlertFORMAT: "APS Signal Fail Due to Excessive Bit Errors on %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Aps SF due to excessive BIP errors. It happens when the bit error rate exceeds the SF threshold on a line."RECOMMENDED ACTION: "Check the line cable on local end and remote end. Check the backcard status on local end and remote end."REQUIRED INFO: No action required. Operational event log only.APS-3-SF_BER_DECL_CLE
SEVERITY: Minor AlertFORMAT: "APS Signal Fail Due to Excessive Bit Errors Cleared on %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Aps SF due to excessive BIP errors cleared.It happens when the bit error rate falls below the SF threshold on a line.Logging the event for informational purpose."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SD
SEVERITY: Minor AlertFORMAT: "APS Signal Degrade Error on %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Aps Line Signal Degrade alarm detected.It happens when the bit error rate exceeds the SD threshold on a line."RECOMMENDED ACTION: "Check the line cable on local end and remote end. Check the backcard status on local end and remote end."REQUIRED INFO: No action required. Operational event log only.APS-3-SD_CLEAR
SEVERITY: Minor AlertFORMAT: "APS Signal Degrade Error Cleared on %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Aps Line SD cleared.It happens when the bit error rate falls below the SD threshold on a line. Logging the event for informational purpose."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-2-PSB_FAIL
SEVERITY: Major AlertFORMAT: "APS Protection Switch Byte Failure on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps PSBF Failure occurs if the APS receives an invalid or an inconsistent K1 byte from remote end. A Protection Switching Byte Defect is detected upon receipt of invalid/inconsistent K1 byte. If the defect persists for 2.5s then a Protection Switching Byte Failure is declared"RECOMMENDED ACTION: "Please check the APS configuration on the remote end. Check if the backcards are connected properly.If redundancy is configured then check if the aps mini backplaneis correctly engaged and the backcards are inserted properly withcorrect alignment on the aps backplane. Also verify that the linesare properly terminated and the contact is good. For further information.please refer to the Bellcore GR-253-CORE document."REQUIRED INFO: No action required. Operational event log only.APS-2-CHAN_MISMATCH
SEVERITY: Major AlertFORMAT: "APS Channel Mismatch on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Chan Mismatch Failure occurs when the channel number indicated by both ends are different."RECOMMENDED ACTION: "Please check if the APS is configured correctly and the APS on the far end is functioning properly.For further information please refer to the Bellcore GR-253-CORE document"REQUIRED INFO: No action required. Operational event log only.APS-4-PSBF_CLEARED
SEVERITY: ErrorFORMAT: "APS Protection Switch Byte Failure Cleared on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "PSBF has been Cleared"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-CHAN_MIS_CLEARE
SEVERITY: ErrorFORMAT: "APS Channel Mismatch Failure Cleared on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "APS Channel mismatch Failure Cleared."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-2-FAR_END_FAIL
SEVERITY: Major AlertFORMAT: "APS Far End Protection Line Failure on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Far End Protection Line Failure occurs when the near end receives a signal fail code for the protection line. This indicates that the far end is no longer receiving the near end's request or considers the near end's request to be invalid. For further information please refer to the Bellcore GR-253-CORE document"RECOMMENDED ACTION: "Please check if the cables at the far end are connected properly."REQUIRED INFO: No action required. Operational event log only.APS-4-FAR_END_FAIL_CL
SEVERITY: ErrorFORMAT: "APS Far End Protection Line Failure Cleared on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Far End Protection Line Failure Cleared"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-2-MODE_MISMATCH
SEVERITY: Major AlertFORMAT: "APS Mode Mismatch on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps mode mismatch detected.This happens when one end is configured in Unidirectional and the other end is in Bidirectional Mode. It can also happen if one end is added in 1+1 architecture and the other end is in 11.This could cause a change in the operating mode.For further information please refer to the Bellcore GR-253-CORE document"RECOMMENDED ACTION: "Check if the mode or the architecture should be same. If they are supposed to be different then this condition will occur."REQUIRED INFO: No action required. Operational event log only.APS-6-MODE_MIS_CLEAR
SEVERITY: NoticeFORMAT: "APS Mode Mismatch Cleared on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps mode mismatch cleared. RxK2 byte mode is same as the Provisioned mode. This could cause a change in the APS operating mode."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_SF
SEVERITY: Minor AlertFORMAT: "APS Internal Switch due to Aps Signal Fail %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Switch due to SF. Traffic may have been affected. It indicates a switch away from the affected line. Logging for informational purposes only."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_SD
SEVERITY: Minor AlertFORMAT: "APS Internal Switch due to Aps Signal Degrade %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Switch due to SD. This command occurs when there's a signal degrade on the line. It indicates a switch away from the affected line. Logging for informational purposes only."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_REV
SEVERITY: Minor AlertFORMAT: "APS Reverse Request Switch %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Reverse Request Switch is generated in response to a remote request like WTR, Forced switch or SF/SD. This causes a switch away from the affected line. This is generated only for APS configured in bidirectional mode Logging for informational purposes only."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_RELEASE
SEVERITY: Minor AlertFORMAT: "APS Switch Cleared. No Pending Request for %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Selector is released. No pending request present Logging for informational purposes only."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_LOCK
SEVERITY: Minor AlertFORMAT: "User Requested APS Lockout successful %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Lockout happened due to User Request. Traffic may have been disturbed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_FORCE_WTOP
SEVERITY: Minor AlertFORMAT: "User Requested APS Forced Work->Prot successful %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Forced W->P Switch happened due to User Request. Traffic may have been disturbed. This will make the APS select from the protection line."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_FORCE_PTOW
SEVERITY: Minor AlertFORMAT: "User Requested APS Forced Prot->Work successful %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Forced P->W Switch happened due to User Request Traffic may have been disturbed. This will make the APS select from the working line."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_ANNXB_FORCE
SEVERITY: Minor AlertFORMAT: "User Requested APS Forced Switch successful %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Forced Switch (Annex-B protocol) happened due to User Request. Traffic may have been disturbed. This will make the APS select from the other Working Section."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_MAN_WTOP
SEVERITY: Minor AlertFORMAT: "User Requested APS Manual Work->Prot successful %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Manual W->P Switch happened due to User Initiated Request. Logging the event for informational purpose."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-SW_MAN_PTOW
SEVERITY: Minor AlertFORMAT: "User Requested APS Manual Prot->Work successful %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Manual P->W Switch happened due to User Initiated Request. Logging the event for informational purpose."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-SW_CLEAR_FAIL
SEVERITY: ErrorFORMAT: "Cannot do APS Switch Clear %s workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Clear Fail. Check the reason displayed in the eventlog."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-SW_LOCK_FAIL
SEVERITY: ErrorFORMAT: "Cannot do APS Switch Lockout %s workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "APS Line Lockout command failed. Check the reason displayed in the eventlog."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-SW_FORCE_WTOP_F
SEVERITY: ErrorFORMAT: "Cannot do APS Switch Forced Work->Prot %s workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Forced W->P Switch fail"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-SW_FORCE_PTOW_F
SEVERITY: ErrorFORMAT: "Cannot do APS Switch Forced Prot->Work %s workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Forced P->W Switch fail"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-SW_MAN_WTOP_FAI
SEVERITY: ErrorFORMAT: "Cannot do APS Manual Switch Work->Prot %s workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Manual W->P Switch fail"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-SW_MAN_PTOW_FAI
SEVERITY: ErrorFORMAT: "Cannot do APS Manual Switch Prot->Work %s workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Manual P->W Switch fail"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-SW_SF_FAIL
SEVERITY: ErrorFORMAT: "APS Internal Switch due to Aps Signal Fail High FAILED %s workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Switch due to SF fail.In normal operation, such an error should never get reported. This may result in traffic loss."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-4-SW_SD_FAIL
SEVERITY: ErrorFORMAT: "APS Internal Switch due to Aps Signal Degrade FAILED %s workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Switch due to SD fail.In normal operation, such an error should never get reported. This may result in traffic loss."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-SW_SERVICE
SEVERITY: NoticeFORMAT: "User Requested APS Service Switch workLN = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Aps Line Service Switch requested by user is successful. Traffic may have been disturbed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-PSB_INCONSISTEN
SEVERITY: NoticeFORMAT: "APS Inconsistent K1 Detected on %s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Inconsistent K1 byte Detection"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-6-PSB_INVALID_DET
SEVERITY: NoticeFORMAT: "APS Invalid K1 req 0x%x and chan 0x%x detected on %s"FLAG: No FlagTHROTTLING: Hundred MillisecondsEXPLANATION: "Invalid K1 byte Detection"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-PRIMARY_SEC_MIS
SEVERITY: Minor AlertFORMAT: "APS Primary Section Mismatch detected on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Primary Section Mismatch Detected. This happens when APS at one end has a different Primary Section than the other end."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.APS-3-PRIMARY_SEC_SWA
SEVERITY: Minor AlertFORMAT: "APS Primary Section Swap on %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Primary Section Swap Occured. This happens when the working sections are swapped and the primary section indicates the other working section."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No action required. Operational event log only.DDTS "drivers"
ATLA-2-AT_INIT_ERROR
SEVERITY: Major AlertFORMAT: "ATLAS Init Error Atlas No %d, line %d, errno %d, info %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: " A hardware error is detected by the ATLAS driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. do core dump"ATLA-4-AT_HW_ERROR
SEVERITY: ErrorFORMAT: "ATLAS HW Error Atlas No %d, line %d, errno %d, info %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: " A hardware error has been detected by ATLAS drive during runtime In normal operation, this kind of error should never happen. This error needs to be analyzed by TAC and possibly by the development team."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. do core dump or register dump3. dspchancnt on affected connections"ATLA-5-AT_WARNING
SEVERITY: WarningFORMAT: "ATLAS Warning Atlas No %d, line %d, errno %d, info %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A warning condition has been detected by ATLAS driver."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection6. do core dump or register dump"ATLA-7-AT_INFOSEVERITY: InformationFORMAT: "ATLAS Info Atlas No %d, line %d, errno %d, info %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "ATLAS Driver Informational Log"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "driver"
DAL-2-DAL_INIT_ERR
SEVERITY: Major AlertFORMAT: "DAL Init Err line %d errno=0x%X,0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the DAL module during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-2-DAL_INIT_ERR_ST
SEVERITY: Major AlertFORMAT: "DAL Init Err line %d errno=0x%X,0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the DAL module driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-4-DAL_ERR
SEVERITY: ErrorFORMAT: "DAL Err line %d errno=0x%X,0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-4-DAL_ERR_STR
SEVERITY: ErrorFORMAT: "DAL Err line %d errno=0x%X,0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-5-DAL_WARNING
SEVERITY: WarningFORMAT: "DAL Warning line %d errno=0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an warning detected by the DAL module."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection"DAL-5-DAL_WARNING_STR
SEVERITY: WarningFORMAT: "DAL Warning line %d errno=0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an warning detected by the DAL module."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection"DAL-7-DAL_INFO
SEVERITY: InformationFORMAT: "DAL Info line %d errno=0x%X,0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DAL Informational Event."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDL-7-DRV_EVENT
SEVERITY: InformationFORMAT: "DDL_EVENT: %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Device Driver Layer Event - more info can be obtained from the error string printed out - applications calling the drivers would log appropriate errors - this is to get detailed info on the specific error experienced by the driver"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "diag"
DIAG-7-LOG
SEVERITY: InformationFORMAT: " OfflnDiag event %s %s\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "OfflnDiag Informational Event"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDIAG-4-ERROR
SEVERITY: ErrorFORMAT: " OfflnDiag error %s %s\n"FLAG: Stack TraceTHROTTLING: No ThrottlingEXPLANATION: "Indicates an internal software error has been detected by OfflnDiag"RECOMMENDED ACTION: "Call your Cisco technical support representative and pass the captured info to the representative."REQUIRED INFO: "Capture the following info from the switch On pxm45 1>dspcd 2>dspver 3>dspcds 4>dsppnports 5>dsplog -sl <slot number of Service Module> 6>dsperr -sl <slot number of Service Module> On the Service Module(SM) 1>dspcd 2>dspver 3>dsplns 4>dspports 5>dspparts 6>dspapslns (for SONET cards)"DDTS "drivers/vsi"
HUMV-2-HV_INIT_ERR
SEVERITY: Major AlertFORMAT: "HUMVEE Init Err line %d, errno=0x%X 0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the HUMVEE driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "HUMV-2-HV_INIT_ERR_STR
SEVERITY: Major AlertFORMAT: "HUMVEE Init Err line %d, errno=0x%X 0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the HUMVEE driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "HUMV-4-HV_HW_ERR
SEVERITY: ErrorFORMAT: "HUMVEE Err line %d, errno=0x%X 0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the HUMVEE driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. do core dump or register dump3. dspchancnt on affected connection "HUMV-4-HV_HW_ERR_STR
SEVERITY: ErrorFORMAT: "HUMVEE Err line %d, errno=0x%X 0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the HUMVEE driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. do core dump or register dump3. dspchancnt on affected connection "HUMV-5-HV_WARN
SEVERITY: WarningFORMAT: "HUMVEE Warning line %d, errno=0x%X 0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an warning detected by the HUMVEE driver."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection6. do core dump or register dump "HUMV-5-HV_WARN_STR
SEVERITY: WarningFORMAT: "HUMVEE Warning line %d, errno=0x%X 0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an warning detected by the HUMVEE driver."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection6. do core dump or register dump "HUMV-7-HV_INFO
SEVERITY: InformationFORMAT: "HUMVEE Info line %d, errno=0x%X 0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "HUMVEE Informational Event."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "ccma"
OAM-7-LOG
SEVERITY: InformationFORMAT: "OAM event %s %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Oam Informational Event"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoOAM-4-ERROR
SEVERITY: ErrorFORMAT: "OAM error %s %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a software error detected by the oam task. Need to contact TAC for the problem."RECOMMENDED ACTION: "Call your Cisco technical support representative and pass the captured info to the representative."REQUIRED INFO: "Capture the following info from the switch On pxm45 1>dspcd 2>dspver 3>dspcds 4>dsppnports 5>dsplog -sl <slot number of Service Module> 6>dsperr -sl <slot number of Service Module> On the Service Module(SM) 1>dspcd 2>dspver 3>dsplns 4>dspports 5>dspparts 6>dspapslns (for SONET cards)"DDTS "drivers"
QE-2-QE_INIT_ERR
SEVERITY: Major AlertFORMAT: "QE Init Err: line %d, errno=0x%X : 0x%X,0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the QE1210 driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives:"REQUIRED INFO: " On PXM45:1. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module:1. dspcd "QE-2-QE_INIT_ERR_STR
SEVERITY: Major AlertFORMAT: "QE Init Err line %d, errno=0x%X 0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the QE1210 driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "QE-4-QE_HW_ERR
SEVERITY: ErrorFORMAT: "QE Err line %d, errno=0x%X 0x%X,0x%X"FLAG: Stack Trace|Write to BramTHROTTLING: No ThrottlingEXPLANATION: "Indicates a hardware error detected by the QE1210 driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. do core dump or register dump3. dspchancnt on affected connection "QE-4-QE_HW_ERR_STR
SEVERITY: ErrorFORMAT: "QE Err line %d, errno=0x%X 0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the QE1210 driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. do core dump or register dump3. dspchancnt on affected connection"QE-5-QE_WARN
SEVERITY: WarningFORMAT: "QE Warning line %d, errno=0x%X 0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an warning detected by the QE1210 driver."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection6. do core dump or register dump "QE-5-QE_WARN_STR
SEVERITY: WarningFORMAT: "QE Warning line %d, errno=0x%X 0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an warning detected by the QE1210 driver."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection6. do core dump or register dump "QE-7-QE_INFO
SEVERITY: InformationFORMAT: "QE Info line %d, errno=0x%X 0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "QE1210 Informational Event."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "drivers"
EFE-5-BADFRBNUM
SEVERITY: WarningFORMAT: "FRB number %d is unacceptable."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEFE-5-BADPORTNUM
SEVERITY: WarningFORMAT: "Port number %d is unacceptable."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEFE-5-BADCRC
SEVERITY: WarningFORMAT: "CRC size %d is unacceptable."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEFE-5-BADHDRSIZE
SEVERITY: WarningFORMAT: "Header size %d is unacceptable."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEFE-5-INITAGAIN
SEVERITY: WarningFORMAT: "%s() Driver already initialized."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "IFE driver getting initialized more than once."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEFE-5-ISRINVOCATION
SEVERITY: WarningFORMAT: "EFE error Error Reg=(0x%08x)"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "EFE Error Occured."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEFE-5-ISRBEFOREINIT
SEVERITY: WarningFORMAT: "%s() ISR called before Init."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "EFE ISR is called before efeInit."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEFE-5-BADADDRESS
SEVERITY: WarningFORMAT: "Bad pointer %p"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "diskdb"
ELS-1-FILEOPENFAIL
SEVERITY: FatalFORMAT: "failed to open event log file"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "failed to open event log file"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoELS-3-WRNGEVTLOG
SEVERITY: Minor AlertFORMAT: "EventLog Server receives a message other than ERR_LOG_MSG"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "EventLog Server Task receives a message other than the message type of ERR_LOG_MSG"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoELS-3-BRAMFAIL
SEVERITY: Minor AlertFORMAT: "BRAM checksum failed %ud, %u d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "BRAM checksum failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoELS-7-TEST_STACK
SEVERITY: InformationFORMAT: "%s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Test for Stack Trace"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "axsme_apps"
EM-2-PATH_ALARM
SEVERITY: Major AlertFORMAT: "%s Failure on %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Specified failure has been detected on the path. A failure is declared after persistency check on a defect. A failure typically indicates data loss at local or remote end. Path failures are generaly a result of transport failure, external to the switch."RECOMMENDED ACTION: "Check the external transport equipment and the far end equipment to identify the root cause."REQUIRED INFO: "dsppathalm will identify the failure(s) for the specified path."EM-3-PATH_ALARM_CLEA
SEVERITY: Minor AlertFORMAT: "%s Failure Cleared on %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Specified failure on the path is now cleared. Failures are cleared after persistency check on clearing of associated defect."RECOMMENDED ACTION: "No action is required. The event is logged to inform the network operator that a previous local/remote failure is now cleared."REQUIRED INFO: No Required InfoEM-4-EM_ERR_STKTRC
SEVERITY: ErrorFORMAT: "EM ERROR: %s\n"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the EM application. It needs to be analyzed by TAC and possibly by the development team. In normal operation, such an error should never get reported."RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative: "REQUIRED INFO: " On PXM45:1. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.On Service Module:1. dspcd2. dsplns3. dspports4. dspparts5. dspapslns (for SONET cards) "EM-4-EM_ERROR
SEVERITY: ErrorFORMAT: "EM ERROR %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the EM application. It needs to be analyzed by TAC and possibly by the development team. In normal operation, such an error should never get reported."RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative "REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.On Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspapslns (for SONET cards) "EM-7-EM_EVENT
SEVERITY: InformationFORMAT: "EM Event %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "EM Informational Event"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEM-2-ONLINE_DIAG_FAI
SEVERITY: Major AlertFORMAT: "ONLINE DIAG ERROR %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicate failure in cell path test. If this happens on an active card with redundancy ready, it will cause a card switch over. Software will not take any action if this happens on an active card without redundancy or on a standby card. When this happens on an active card, the card will experience traffic loss and its likely to see some other errors"RECOMMENDED ACTION: "First please collect the following info. If this happens on an active card without redundancy or on a standby card, manually reset the card. If reset fails, need to replace the front card.Then call your Cisco technical support representative for the problem."REQUIRED INFO: "Capture the following info On Pxm45 1> dspcd 2> dspcds 3> dsplog -sl <slot number of service module> 4> dsperr -sl <slot number of service module> On Service Module(SM) 1> dspcd 2> dspver 3> dspports"EM-2-NOVRAM_READ_ERR
SEVERITY: Major AlertFORMAT: "NOVRAM Read Error %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This error indicates a failure reading the NOVRAM. This failure can be for one of the following NOVRAMs1. Front Card NOVRAM2. Daughter Card NOVRAM3. Back Card NOVRAM"RECOMMENDED ACTION: "If the error is indicated for Front Card or Daughter Card NOVRAM, please replace the Front Card. Replace the Back Card if error is indicated for Back Card NOVRAM. In most cases, NOVRAM read failures are a direct result of a hardware failure. However, if you suspect that the error was caused due a certain operator action or a system event, please capture the following information and contact your Cisco support representative "REQUIRED INFO: "Please capture following information on PXM451. dspcds2. dspcd <slot>3. dsplogOn Service Module, please capture the following information1. dspcd2. dsplns "EM-2-LINE_HARDWARE_E
SEVERITY: Major AlertFORMAT: "Line Hardware Error on line %d.%d\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This error indicates a hardware failure for the specified line. The failure is typicaly due to a front-card hardware problem."RECOMMENDED ACTION: "Please replace the Front Card if the problem persists across reboots. Note that if this error is detected on a standby card, it will automaticaly reboot. If the error is detected on an active card, the card will continue to function. However, the dspcds command on PXM45 will show that the card state is Active-F. Contact your Cisco support representative if you suspect that a certain operator action or a system event caused this error."REQUIRED INFO: "Please capture the information with following commands on the active service module1. dspcd2. dsplns3. dspalmsPlease capture the system log with dsplog <slot> command on PXM45."EM-2-DAUGHTER_CARD_M
SEVERITY: Major AlertFORMAT: "Unknown/Missing Daughter Card on bay %d\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This error indicates a failure in recognizing the Daughter Card in the specified bay. This can happen due to one of the followng reasons1. Daughter Card NOVRAM is not readable2. Daughter Card Type specified by NOVRAM is not supported3. A Daughter Card is not installed.This error is detecting during the booting phase. "RECOMMENDED ACTION: "Please replace the Front Card as it is not usable. Note that this error will take the card in Active-F state. If the error is detected on a standby card, it will cause the card to reset. Please capture following information and contact your Cisco support representative if you suspect that a certain operator action or a system event caused this error "REQUIRED INFO: "Please capture following information on PXM451. dspcds2. dspcd <slot>3. dsplogOn Service Module, please capture the following information1. dspcd2. dsplns "EM-2-PRTSTAT
SEVERITY: Major AlertFORMAT: "Port State Port%d Oper State%s \n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Change in port operation state. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_ERROR to make it more visible for customer."RECOMMENDED ACTION: "Port operation state changes according to line state. Check line for alarms and take appropriate corrective actions on physical line."REQUIRED INFO: No Required InfoDDTS "cema"
EM-2-TASKINIT
SEVERITY: Major AlertFORMAT: "ERROR 0x%x CEMA application initialization failure"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Error occurred during CEMA application initialization. The error is fatal if it prevents the AXSM from going to the card ready state. When this happens, AXSM gets reset."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverIf AXSM does eventually come up, on AXSM1. dspcd2. dsdver3. dsplns4. dspports5. dspparts6. dspapslns (SONET cards only)7. dspilmis8. dsplmisNote whether event is logged during to card reset or switchover."EM-4-CPICMD
SEVERITY: ErrorFORMAT: "ERROR 0x%x General CPI command failure"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error occurred while processing CPI command"RECOMMENDED ACTION: "Retry CLI commands. Failure can sometimes be temporarily. If error persists, 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."REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverOn AXSM1. dspcd2. dspver "EM-4-DISKERR
SEVERITY: ErrorFORMAT: "Disk failure Error 0x%x, %s, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error is detected while accessing disk from AXSM. The detail error type is the Error field in the event log. If this happens as a result of CLI, it simply means that disk update for this CLI fails and the CLI is rejected. If this happens during card initialization, some configuration prior to card reset may be lost and service can probably be impacted. This event log is usually accompanied by a corresponding SSI disk event log which contains more error details."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverOn AXSM1. dspcd2. dspver3. dsplns4. dspports5. dspparts6. dspapslns (SONET cards only)7. dspilmis8. dsplmisNote whether event is logged during card reset or switchover. If card is reset, note if it is a consequence of setrev/loadrev/runrev. "EM-4-IPCERR
SEVERITY: ErrorFORMAT: "IPC failure Error 0x%x, %s, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error occurred while making IPC function call. This event log is usually accompanied by a corresponding IPC event log."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverOn AXSM1. dspcd2. dspver "EM-4-IPCERR_EM_SEND
SEVERITY: ErrorFORMAT: "IPC failure Error 0x%x, %s, 0x%x, 0x%x\n"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Error occurred while making IPC function call. This event log is usually accompanied by a corresponding IPC event log. This is called when Error in sendEmReq."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverOn AXSM1. dspcd2. dspver "EM-4-SWERR
SEVERITY: ErrorFORMAT: "SW error Error 0x%x, %s, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Miscellaneous software error occurred."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverOn AXSM1. dspcd2. dspver3. dsplns4. dspports5. dspparts6. dspapslns (SONET cards only) "EM-4-PHYERR
SEVERITY: ErrorFORMAT: "PHY error Error 0x%x in function %s, line %d.%d\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error occurred while making PHY module function call. It can be service impacting if error results in line not being configured properly. "RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverOn AXSM1. dspcd2. dspver3. dsplns4. dspapslns (SONET card only) "EM-4-VSIERR
SEVERITY: ErrorFORMAT: "VSI error Error 0x%x, %s, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error occurred while making VSI module function call. It can be service impacting if error results in port and partitions not being configured properly. "RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverOn AXSM1. dspcd2. dspver3. dsplns4. dspports5. dspparts "EM-2-DATAERR
SEVERITY: Major AlertFORMAT: "EM database consistency error 0x%x, %s, %d, %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Database inconsistency has been detected. For example, a port exists on a line that has not been upped. In this case, the port is deleted as a corrective action to restore database consistency. Database consistency is only checked during card reset of switchover. The resulting change can cause system to work differently than before inconsistency is detected."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.7. cd DDB28. change to disk DB directory for primary slot. For example, slot 11disk DB is in directory LS11.9. dirOn AXSM1. dspcd2. dspver3. dsplns4. dspports5. dspparts6. dspapslns (SONET cards only)Note whether event is logged during card reset or switchover. If card is reset, note if it is a consequence of setrev/loadrev/runrev. "EM-6-LOG
SEVERITY: NoticeFORMAT: "EM LOG %s, %d, %ld, %ld\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Miscellaneous software error occurred."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.On AXSM1. dspcd2. dspver3. dsplns4. dspports5. dspparts6. dspapslns (SONET cards only) "EM-4-APSERR
SEVERITY: ErrorFORMAT: "APS error Error 0x%x, %s, %d, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error occurred while making APS module function call."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.On AXSM1. dspcd2. dspver3. dsplns4. dspapslns (SONET cards only) "EM-4-GENERR
SEVERITY: ErrorFORMAT: "%s error Error 0x%x, %s, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error as depicted in event log occurred."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.On AXSM1. dspcd2. dspver3. dsplns4. dspports5. dspparts6. dspapslns (SONET cards only) "EM-4-GENERB
SEVERITY: ErrorFORMAT: "%s error Error 0x%x, %s, 0x%x, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error as depicted in event log occurred."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.On AXSM1. dspcd2. dspver3. dsplns4. dspports5. dspparts6. dspapslns (SONET cards only) "EM-2-PHYALM
SEVERITY: Major AlertFORMAT: "PHY line alarm Line %d.%d %s\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Red line alarm has been detected. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_MAJOR_ALERT at the request by customer to make it more visible."RECOMMENDED ACTION: "Line alarms are part of normal operation. Use dspalm, dspln and dspatmcnf type commands to find out alarms and line configuration. Check physical line cables to see that they are properly installed. Check that the line configurations are correct since alarms can sometimes be due to incompatible line type. Follow normal network procedure to isolate line fault in network."REQUIRED INFO: "Issue dspver on AXSM to get AXSM SW version and date image was built."EM-2-PHYALM_MINOR
SEVERITY: Major AlertFORMAT: "PHY line alarm minor Line %d.%d %s\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Minor line alarm has been detected. It can be remote alarm or minor APS-relalted alarm. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_MAJOR_ALERT at the request by customer to make it more visible."RECOMMENDED ACTION: "Line alarms are part of normal operation. Use dspalm, dspln and dspatmcnf type commands to find out alarms and line configuration. Check physical line cables to see that they are properly installed. Check that the line configurations are correct since alarms can sometimes be due to incompatible line type. Follow normal network procedure to isolate line fault in network."REQUIRED INFO: "Issue dspver on AXSM to get AXSM SW version and date image was built."EM-2-PHYALM_CLR
SEVERITY: Major AlertFORMAT: "PHY line alarm cleared Line %d.%d %s\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Line alarm as mentioned in event is cleared. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_MAJOR_ALERT at the request by customer to make it more visible."RECOMMENDED ACTION: "No action is required. The event is logged to inform the network operator that a previous local/remote failure is now cleared."REQUIRED INFO: No Required InfoEM-2-PRTSTAT
SEVERITY: Major AlertFORMAT: "Port State Port%d Oper State%s \n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Change in port operation state. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_MAJOR_ALERT to make it more visible for customer."RECOMMENDED ACTION: "Port operation state changes according to line state. Check line for alarms and take appropriate correction actions on physical line."REQUIRED INFO: No Required InfoEMRO-2-TASKINIT
SEVERITY: Major AlertFORMAT: "EM Root failure 0x%x, %s, %d, %d"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Error occurred during CEMA application initialization. The error is fatal if it prevents the AXSM from going to the card ready state. When this happens, AXSM gets reset."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverIf AXSM does eventually come up, on AXSM1. dspcd2. dsdpver3. dsplnsNote whether event is logged during to card reset or switchover."EMRO-7-EMINFO
SEVERITY: InformationFORMAT: "%s\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "This event is for developer information purpose."RECOMMENDED ACTION: "No Action is required since it is only informational and not service impacting."REQUIRED INFO: "None Required"DDTS "axsme_apps"
EM-2-LINE_ALARM
SEVERITY: Major AlertFORMAT: "Local Failure on%sLine %d.%d, Cause %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Specified line has a local failure. A failure is declared after persistency check on the defect. It indicates that the switch is unable to receive user data from the specified line. The log also identifies the cause for the failure. Failures can be declared due to removal of back card,cable disconnection or any physical disconnection with the remote equipment."RECOMMENDED ACTION: "Check if the back card and cable are installed. Check the status of remote equipment. This log typicaly indicates an external problem."REQUIRED INFO: "dspalm will identify the failure(s) for the specified line."EM-3-REMOTE_LINE_ALA
SEVERITY: Minor AlertFORMAT: "Remote Failure on%sLine %d.%d, Cause %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Specified line has a remote-end failure. A failure is declared after persistency check on the defect. It indicates that the data transmited on the specified line is not reaching the other end. As a result the remote end is reporting a defect."RECOMMENDED ACTION: "Check if the back card and cable are installed. This log typicaly indicates an external problem."REQUIRED INFO: "dspalm will identify the failure(s) for the specified line."EM-3-LINE_ALARM_CLEA
SEVERITY: Minor AlertFORMAT: "All Failures Cleared on%sLine %d.%d.\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "All failures (local and remote) on the line are cleared"RECOMMENDED ACTION: "No action is required. The event is logged to inform the network operator that a previous local/remote failure is now cleared."REQUIRED INFO: No Required InfoDDTS "pnnisys"
SYS-5-QCOUNT
SEVERITY: WarningFORMAT: "Bad %s %x count %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "An internal software error occurred."RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."SYS-5-NOTQ
SEVERITY: WarningFORMAT: "%s didn't find %x in queue %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "An internal software error occurred."RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."SYS-5-LINKED
SEVERITY: WarningFORMAT: "Bad %s of %x in queue %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "An internal software error occurred."RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."SYS-6-TABLEERR
SEVERITY: NoticeFORMAT: "%s table %s damaged %s."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An internal table entry became corrupt."RECOMMENDED ACTION: "Copy the message exactly as it appears, and report it your technical support representative."REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."SYS-5-BADLIST
SEVERITY: WarningFORMAT: "Regular expression access check with bad list %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "A software error occurred."RECOMMENDED ACTION: "Copy the error message exactly as it appears, and report it to your technical support representative."REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."DDTS "ilmi"
ILMI-4-ERROR
SEVERITY: ErrorFORMAT: "ILMI Internal Err%s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "It describes internal errors(ILMI protocol related) for ILMI module on PNNI controller"RECOMMENDED ACTION: "Check the ILMI status on each interface and figure out which interface has ILMI status changed or error.Record the abnormal behavior and gather all the ILMI and interface related information, and then contact your TAC representative."REQUIRED INFO: "Collect node info on PNNI controller using dspver,dspcds,dsppnports; collect ILMI log using (dsplog -mod ILMI);if specific port is known,collect ILMI info on this port using (dsppnilmi portId).It is also helpful to gather IFM log using (dsplog -mod IFM)"ILMI-5-WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "drivers"
FDM-5-NOFDM
SEVERITY: WarningFORMAT: "%s() FREEDM device not exist."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unable to detect FREEDM device."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-INVALIDPARAM0
SEVERITY: WarningFORMAT: "%s() Invalid parameters pFdmDev = 0x%x bDoReset = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-NOTFOUND
SEVERITY: WarningFORMAT: "%s() FREEDM# %d Incorrect device ID = 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unrecognized FREEDM device ID."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-INITAGAIN
SEVERITY: WarningFORMAT: "%s() Driver already initialized."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "FREEDM driver got initialize more than once."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-FAILISR
SEVERITY: WarningFORMAT: "%s() Fail to install ISR."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to install ISR."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-INVALIDPARAM1
SEVERITY: WarningFORMAT: "%s() Invalid parameter pFdmDev = 0x%x pParam = 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-INVALIDSTATE0
SEVERITY: WarningFORMAT: "%s() not in eFDM_RESET state - state = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Must be in eFDM_RESET state to do initialization."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-INVALIDPARAM2
SEVERITY: WarningFORMAT: "%s() Invalid parameter pFdmDev = 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid FREEDM device descriptor pointer."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-INVALIDSTATE1
SEVERITY: WarningFORMAT: "%s() Not in eFDM_INIT state - state = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Must be in eFDM_INIT to do activation."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-INTENFAIL
SEVERITY: WarningFORMAT: "%s() Failed to enable interrupt."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Cannot enable interrupt."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-INVALIDPARAM3
SEVERITY: WarningFORMAT: "%s() Invalid parameter pFdmDev = 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid FREEDM device descriptor pointer."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-DEACTFAIL
SEVERITY: WarningFORMAT: "%s() Deactivation failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to deactivate the FREEDM device."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-POLLBUSY
SEVERITY: WarningFORMAT: "%s() FREEDM# = %d Offset = 0x%x Bit mask = 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "FREEDM device busy."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-LINKINVPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameter(s) pFdmDev = %x portType = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-FIFOINVPARAM
SEVERITY: WarningFORMAT: "%s() Invalid param pFdmDev=%x u16BlockStart=%d u16BlockEnd=%d txRx=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameters."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-FIFOCREATE
SEVERITY: WarningFORMAT: "%s() Unable to create channel FIFO %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed FIFO create."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-ICNFPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameter pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-ICNFFAIL
SEVERITY: WarningFORMAT: "%s() Ingress port configuration failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Port configuration failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-ECNFPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameter pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-ECNFFAIL
SEVERITY: WarningFORMAT: "%s() Egress port configuration failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Port configuratiuon failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-IADDPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameter pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-IADDFAIL
SEVERITY: WarningFORMAT: "%s() Ingress port add failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Port add failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-EADDPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameter pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-EADDFAIL
SEVERITY: WarningFORMAT: "%s() Egress port add failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Port add failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-IDELFAIL
SEVERITY: WarningFORMAT: "%s() Ingress delete port failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Ingress port delete failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-EDELFAIL
SEVERITY: WarningFORMAT: "%s() Egress delete port failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Egress port delete failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-ENBDSBPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameter action = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-ENBDSBFAIL
SEVERITY: WarningFORMAT: "%s() Disable port failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Disable port failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-PORTTYPE
SEVERITY: WarningFORMAT: "%s() Non-supported port type %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Port type not supported."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-RXPROVPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameters pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-TXPROVPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameters pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-RXUNPROVPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameters pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-TAVAIL
SEVERITY: WarningFORMAT: "%s() Timeout waiting for TAVAIL"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Transaction still pending."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-TXUNPROVPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameters pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-IPROVPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameters pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-IGRPROVGET
SEVERITY: WarningFORMAT: "%s() Ingress channel is not provisioned"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Channel not provisioned."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-EPROVPARAM
SEVERITY: WarningFORMAT: "%s() Invalid parameters pParam = %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid parameter."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFDM-5-EGRPROVGET
SEVERITY: WarningFORMAT: "%s() Egress channel is not provisioned."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Channel not provisioned."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "control-point"
FMGM-7-FM_OPEN_PASSD
SEVERITY: InformationFORMAT: "%s slotNum %d, reqType %d, Msg %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Open API of the specified file passed."RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFMGM-4-FM_OPEN_FAIL
SEVERITY: ErrorFORMAT: "%s slotNum %d, reqType %d, Msg %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Open API of the specified file failed."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-5-FM_INVD_DESC
SEVERITY: WarningFORMAT: "%s status %d, routine %p, Msg %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid request descriptor."RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-5-FM_INVLD_DESC
SEVERITY: WarningFORMAT: "%s Msg %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid request descriptor."RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_INVLD_SLOT
SEVERITY: ErrorFORMAT: "%s slot number is %d, Msg is %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid slot number."RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-5-FM_MQ_FLSH
SEVERITY: WarningFORMAT: "%s %s Message queue id is %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error trying to flush message queue"RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_SEM_FAIL
SEVERITY: ErrorFORMAT: "%s %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Semaphore creation failed"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-5-FM_STAKE_FAIL
SEVERITY: WarningFORMAT: "%s %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Semaphore take failed"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_INVD_SLOT
SEVERITY: ErrorFORMAT: "%s slot number is %d, card state is %d, card type is %d, Msg is %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid slot number."RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_INVD_FNAME
SEVERITY: ErrorFORMAT: "%s Msg is %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid File Name."RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_INVD_PARAM
SEVERITY: ErrorFORMAT: "%s parameter is %d, Msg is %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid input parameter."RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_NOT_CBSM
SEVERITY: ErrorFORMAT: "%s slot number is %d, card type is %d, Msg is %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Card Type not supported."RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_IPC_ERR
SEVERITY: ErrorFORMAT: "%s %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Obtained ERROR from an IPC message."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_BUF_ERR
SEVERITY: ErrorFORMAT: "%s %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Unable to allocate frame buffer."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_SCM_FAIL
SEVERITY: ErrorFORMAT: "%s slotNum is %d, operation is %d, request is %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Unable to do intercard communication thru SCM."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_MSG_FAIL
SEVERITY: ErrorFORMAT: "%s %s Original message sent slotNum is %d, operation is %d, request is %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Bad response from SM"RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogFMGM-4-FM_RSP_FAIL
SEVERITY: ErrorFORMAT: "%s %s opType received is %d,status received is %d, blockNum received is %d,offSet received is %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failure response received from SM"RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplogDDTS "control-point/pxm-connmgm"
FILM-7-SM_BOOT_DNLD_PA
SEVERITY: InformationFORMAT: "%s Backup Boot Download passed for Slot %d"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Backup Boot was downloaded to the Service Module successfully."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFILM-7-SM_FW_DNLD_PASS
SEVERITY: InformationFORMAT: "%s Firmware Download passed for Slot %d"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Firmware was downloaded to the Service Module successfully."RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFILM-7-PXM_FW_DNLD
SEVERITY: InformationFORMAT: "Downloaded PXM Revision %s "FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "This information event indicates that PXM Firmware has been downloaded."RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFILM-7-PXM_BKUP_DNLD
SEVERITY: InformationFORMAT: "Downloaded PXM Backup Boot, Revision %s "FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "PXM Backup BootCode has been downloaded."RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFILM-7-MSG_SEND_TO_SM
SEVERITY: InformationFORMAT: "%s %s slotNum is %d, opType is %d, fileType is %d"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Message send to SM."RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFILM-7-MSG_RCVFROM_SM
SEVERITY: InformationFORMAT: "%s %s optype is %d, status is %d, blockNum is %d, offSet is %d"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Message received from SM."RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFILM-4-BASISTSKSPWNERR
SEVERITY: ErrorFORMAT: "%s Spawn Task Failed , TaskName %s, Slot No %d, File Type %d"FLAG: Stack TraceTHROTTLING: One SecondEXPLANATION: "Unable to create a new task."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-7-TFTP_NOT_ALLWD
SEVERITY: InformationFORMAT: "%s slotNum %d, fileType %d, card type %d, Msg %s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Specified command not allowed for this Card type"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFILM-5-MSGQ_ERR
SEVERITY: WarningFORMAT: "QName %s, SlotNo %d, FileType %d, Msg %s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Unable to create a message queue."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-5-BUF_ALLOC
SEVERITY: WarningFORMAT: "%s %s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Unable to allocate frame buffer."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-4-PARMINVALID
SEVERITY: ErrorFORMAT: "Parm %s value '0x%x' is invalid to %s."FLAG: Stack TraceTHROTTLING: One SecondEXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-5-DISKWRITEFAIL
SEVERITY: WarningFORMAT: "%s Write to disk failed, fileType is %d"FLAG: Stack TraceTHROTTLING: One SecondEXPLANATION: "Unable to write file to disk."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-5-MSGQFLUSH
SEVERITY: WarningFORMAT: "%s %s Message queue id is %d"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Error trying to flush message queue"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-5-MSG2SCMFAIL
SEVERITY: WarningFORMAT: "%s slotNum is %d, opType is %d, fileType is %d"FLAG: Stack Trace | Dump TraceTHROTTLING: One SecondEXPLANATION: "Unable to do intercard communication thru SCM."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-5-RSP_FAIL_RCVD
SEVERITY: WarningFORMAT: "%s %s opType received is %d, status received is %d, blockNum received is %d, offSet received is %d"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Failure response received from SM"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-5-FAIL_RSP
SEVERITY: WarningFORMAT: "%s %s Original message sent slotNum is %d, opType is %d, fileType is %d"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Bad response from SM"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-4-FW_DNLD_FAILED
SEVERITY: ErrorFORMAT: "Failure Msg %s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Firmware download failed."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-5-FOPEN_FAILED
SEVERITY: WarningFORMAT: "%s slotNum %d, fileType %d, Msg %s"FLAG: Stack TraceTHROTTLING: One SecondEXPLANATION: "Open API of the specified file failed."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-7-FOPEN_PASSED
SEVERITY: InformationFORMAT: "%s slotNum %d, fileType %d, Msg %s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Open API of the specified file passed."RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFILM-5-FREAD_FAILED
SEVERITY: WarningFORMAT: "%s fD %d, slotNo %d, fileType %d, Msg %s"FLAG: Stack TraceTHROTTLING: One SecondEXPLANATION: "File read failed."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-5-FWRITE_FAILED
SEVERITY: WarningFORMAT: "%s fD %d, slotNo %d, fileType %d, Msg %s"FLAG: Stack TraceTHROTTLING: One SecondEXPLANATION: "File write failed."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoFILM-7-FCLOSE_EVENT
SEVERITY: InformationFORMAT: "%s slotNum %d, fileType %d, Msg %s"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Closing the specified file."RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoFILM-5-COMPARE_EVT
SEVERITY: WarningFORMAT: "%s Param1 %d, Param2 %d, slotNo %d, fileType %d, Msg %s"FLAG: Stack TraceTHROTTLING: One SecondEXPLANATION: "Card Type doesn't match the image header."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoTFTP-5-SOCKET_ERR
SEVERITY: WarningFORMAT: "%s Failed to Receive on Socket %d"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Received Error while trying to read data from tftp socket."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoTFTP-4-TASK_SPAWN_ERR
SEVERITY: ErrorFORMAT: "%s Spawn Task Failed , TaskName %s, TaskPriority %d, TaskStackSize %d"FLAG: Stack TraceTHROTTLING: One SecondEXPLANATION: "Spawning of a task failed."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoDDTS "frs"
FRS-5-INVALID_INIT_CA
SEVERITY: WarningFORMAT: "FRS INVALID_INIT_CALL Code=(%u) #InitCalls=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-API_CALL_WITHOU
SEVERITY: WarningFORMAT: "FRS API_CALL_WITHOUT_INIT Code=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-NULL_PTR_ARGS
SEVERITY: WarningFORMAT: "FRS NULL_PTR_ARGS Code=(%u) Ptr=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-STATS_ENABLE_UP
SEVERITY: WarningFORMAT: "FRS STATS_ENABLE_UPDATE_ERROR Code=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-RESETDEVICE_INV
SEVERITY: WarningFORMAT: "FRS RESETDEVICE_INVALID_DEV_BITMAP Code=(%u) BitMap=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_INTERRU
SEVERITY: WarningFORMAT: "FRS INVALID_INTERRUPT_TYPE Code=(%u) INVALID_INTERRUPT_TYPE=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-6-INTERRUPT_INVOC
SEVERITY: NoticeFORMAT: "FRS INTERRUPT_INVOCATION Reg=(0x%08x)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_SELECT_
SEVERITY: WarningFORMAT: "FRS INVALID_SELECT_DECODE Code=(%u) selectDecode=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_DEVICEN
SEVERITY: WarningFORMAT: "FRS INVALID_DEVICENUM Code=(%u) DeviceNum=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_FLAGBIT
SEVERITY: WarningFORMAT: "FRS INVALID_FLAGBITPOS Code=(%u) flagBitPos=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_CONFIGM
SEVERITY: WarningFORMAT: "FRS CONFIGMAP Code=(%u) configMap=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_CHAN_NU
SEVERITY: WarningFORMAT: "FRS INVALID_CHAN_NUM_ARG Code=(%u) Chan=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_PORT_NU
SEVERITY: WarningFORMAT: "FRS INVALID_PORT_NUM_ARG Code=(%u) Port=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_CHAN_ST
SEVERITY: WarningFORMAT: "FRS INVALID_CHAN_STATS_RANGE Code=(%u) ChanBeg=(%u) nChans=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-DMA_ERROR_GET_C
SEVERITY: WarningFORMAT: "FRS DMA_ERROR_GET_CHAN_STATS Code=(%u) ChanBeg=(%u) nChans=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_PORT_IN
SEVERITY: WarningFORMAT: "FRS INVALID_PORT_IN_LMI_ALM_CALL Code=(%u) Port=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INVALID_PORT_OU
SEVERITY: WarningFORMAT: "FRS INVALID_PORT_OUT_OF_LMI_ALM_CALL Code=(%u) Port=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-DMA_TIMEOUT
SEVERITY: WarningFORMAT: "FRS DMA_TIMEOUT Code=(%u) srcPtr=(%u) destPtr=(%u) nBytes=(%u) TickCount=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRS-5-INNER_FUNCTION_
SEVERITY: WarningFORMAT: "FRS INNER_FUNCTION_FAILED Code=(%u)\n"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "ccma"
DAL-4-DALERR
SEVERITY: ErrorFORMAT: "DAL Error %s() line %d %X,%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-4-DALERR_STR
SEVERITY: ErrorFORMAT: "DAL Error %s() line %d %X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-4-DALAVLERR
SEVERITY: ErrorFORMAT: "DAL Internal Error line %d %s,%u,%u,%u"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates error in DAL AVL tree. It needs to be analyzed by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dspcons -filt 8"DAL-7-FPGA
SEVERITY: InformationFORMAT: "FPGA upload/dnload %s, %s, 0x%x, 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates FPGA upload/dnload progress"RECOMMENDED ACTION: "No action is required. Event is logged to show FPGA upload/dnload progress"REQUIRED INFO: No Required InfoDAL-4-FPGAERR
SEVERITY: ErrorFORMAT: "FPGA upload/dnload error %s, %s, 0x%x, 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates error is encountered during FPGA upload/dnload progress"RECOMMENDED ACTION: "No action is required. Event is logged to show FPGA upload/dnload progress"REQUIRED INFO: "On PXM451. dspcds2. dspcd <slot that experienced the error>3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.6. dspverOn FRSM121. dspcd2. dsdpver3. If shell command access is available, excecute dspFpgaRevs shell command "DDTS "drivers"
FRSM-5-NOS4XD3F
SEVERITY: WarningFORMAT: "%s() FRMR device not exist."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unable to detect SUNI4XD3F device."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-LDRV_SET_PARAM_
SEVERITY: WarningFORMAT: "%s() DRV_set param fails line#%d, data %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "LDRV_set param fails."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-INVALIDPARAM_LI
SEVERITY: WarningFORMAT: "%s() Invalid parameter line#%d, lineType %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-INVALIDPARAM_LI
SEVERITY: WarningFORMAT: "%s() Invalid parameter line#%d, lineLength %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-INVALIDPARAM_CL
SEVERITY: WarningFORMAT: "%s() Invalid parameter line#%d, txClkSrc %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-INVALIDPARAM_CH
SEVERITY: WarningFORMAT: "%s() Invalid parameter line#%d, checkAIS %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-INVALIDPARAM_FE
SEVERITY: WarningFORMAT: "%s() Invalid parameter line#%d, FEAC criteria %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-INVALIDPARAM_OO
SEVERITY: WarningFORMAT: "%s() Invalid parameter line#%d, OOF criteria %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed parameter check."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-INITTDMFAIL
SEVERITY: WarningFORMAT: "%s() Init TDM fails."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed TDM initialization."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-TCC4BADDEVICEID
SEVERITY: WarningFORMAT: "%s() TCC4 has wrong device ID."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Wrong TCC4 device ID."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-TCC4RESETFAIL
SEVERITY: WarningFORMAT: "%s() TCC4 reset fails."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "TCC4 fails during reset."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFRSM-5-BCC3WRONGREVISI
SEVERITY: WarningFORMAT: "%s() Backcard BCC3 has wrong revision."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Wrong backcard BCC3 revision."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "pxm-connmgm"
FTM-7-TASKINIT
SEVERITY: InformationFORMAT: "Init Error %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Task Initialization Error"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredFTM-7-MSGPROC
SEVERITY: InformationFORMAT: "Message Proc Error %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Message Processing Errors"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Please capture the following information from the PXM45 cli and call your TAC support1) dspcds/dspcd2) dspver3) dsplog -sl <slot which is experiencing the problem>4) dsplog -sl < redundant slot if configured>5) dsperr for the above slots.6) Save the core file if requiredFTM-7-TRAPPROC
SEVERITY: InformationFORMAT: "Trap Proc Error %s %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Trap Processing Errors"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoDDTS "fw-download"
FTPD-5-FTPD_DIR_FOUND
SEVERITY: WarningFORMAT: "EVNT Directory %s found, No need to create"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: " found directory"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FTPD_NON_DIR_FI
SEVERITY: WarningFORMAT: "ERRfound a non directory entry of name %s found."FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: " found a non directory entry of name FTPD"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FTPD_OPEN_FAILE
SEVERITY: WarningFORMAT: "ERR unable to open dir/file %s "FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: " unable to call open for FTPD"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-4-FTPD_MKDIR_FAIL
SEVERITY: ErrorFORMAT: "ERR unable to do create directory %s "FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: " unable to create dir for FTPD"RECOMMENDED ACTION: "Make sure C\TMP exists. If not, create one and re-ftp the file. If the problem persist, please contact TAC"REQUIRED INFO: "Capture the output of 'dir C'"FTPD-7-FTPD_VXWORKS_FA
SEVERITY: InformationFORMAT: "EVNT%s %s "FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: " unable to call vxworks call"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-7-FTPD_API_ERROR
SEVERITY: InformationFORMAT: "EVNTApi returns error, api=%s, errno 0x%x "FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: " API returns error. Need to look at errno"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-4-FTPD_REPLCTN_FA
SEVERITY: ErrorFORMAT: "ERR Replication request FAILED for %s, errno=0x%x"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Replication request failed"RECOMMENDED ACTION: "File replication to standby PXM failed. Contact TAC to manually copy the file over."REQUIRED INFO: "Capture the following commands1) dsplog -mod FTPD2) dsplog -mod SSI3) dsplog "FTPD-5-FTPD_REPLCTN_ER
SEVERITY: WarningFORMAT: "ERR %s NOT REPLICATED ON STBY "FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Replication request failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FTPD_REPLCTN_ER
SEVERITY: WarningFORMAT: "ERR %s not copied.Exists as %s "FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Replication request failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FTPD_REP1
SEVERITY: WarningFORMAT: "EVNTFTP Replicate usr file %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "log event to note replication request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FTPD_REP2
SEVERITY: WarningFORMAT: "EVNTFTP from file %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "log event to note replication request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-4-FTPDLIB1
SEVERITY: ErrorFORMAT: "ERR - %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "error spawning ftp task"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: "Capture the following commands1) dsplog -mod FTPD2) dsplog"FTPD-7-FTPDLIB2
SEVERITY: InformationFORMAT: "EVNT%s %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "login verification failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-7-FTPDLIB3
SEVERITY: InformationFORMAT: "EVNT%s %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "usr logged on/off"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-7-FTPDLIB4
SEVERITY: InformationFORMAT: "EVNT %s %s, errno = 0x%x"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "cannot get/put a file - file locked"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-7-FTPDLIB5
SEVERITY: InformationFORMAT: "EVNT %s %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "unauthorized user attempting to write to disk"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FTPDLIB6
SEVERITY: WarningFORMAT: "EVNT %s %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "put request failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-7-FTPDLIB7
SEVERITY: InformationFORMAT: "EVNT%s %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "error while receiving data from socket for a get request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-7-FTPDLIB8
SEVERITY: InformationFORMAT: "EVNTPUT request completed sucessfully. user=%s, file_name=%s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "Logged a put request by a user"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FTPDSIZEMISMATC
SEVERITY: WarningFORMAT: "EVNTFile size on disk (%ld) is different from bytes transferred (%d) for file %s"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "File size on disk is different from the bytes transferred."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FILELOCKED
SEVERITY: WarningFORMAT: "File will remain locked till you reset gFtpLockOnSizeMismatch.Use shellconftpdLockOnSizeMismatchOff() or ftpdLockOnSizeMismatchSet(value)--value can be 0 or 1 or 2 "FLAG: No FlagTHROTTLING: Two MinutesEXPLANATION: "File size on disk is different from the bytes transferred."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-SEMTAKEFAIL
SEVERITY: WarningFORMAT: "%sFailed to take semaphore %sfname%s,size%d,dataskt%d,ctlSkt%d,byteXfer%d"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "While trying to update the audit log, the task mentioned, failed to take the semaphore. It will return without updating the audit log"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFTPD-5-FTPD_ACCEPT_FAI
SEVERITY: WarningFORMAT: "EVNT A call to socket API Accept() failed. Line=%d, errno=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: " A call to socket API accept() to accept connections for FTP failed"RECOMMENDED ACTION: " No recommended action, as the system should recover automatically"REQUIRED INFO: No Required InfoFTPD-7-FTPD_CMDSEND_ER
SEVERITY: InformationFORMAT: "EVNT%dFailed to send command %d, errno 0x%x "FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "FTPD failed to send a command on control socket to the other end. Need to look at errno"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "hw-poll"
HMM_-2-XBAR_PLANE_RST
SEVERITY: Major AlertFORMAT: "XBAR plane is in reset state on Switch Card %d, plane %d"FLAG: No FlagTHROTTLING: No ThrottlingEXPLANATION: "XBAR plane is in reset state"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.HMM_-7-XBAR_DEVPTR_NUL
SEVERITY: InformationFORMAT: "Line %d: HMM returned DevPtr= Null ,DevId %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "HMM Dev Ptr access failed and returned NULL"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoHMM_-7-DEVPTR_NULL
SEVERITY: InformationFORMAT: "Line %d: HMM returned DevPtr= Null ,DevId %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "HMM Dev Ptr access failed and returned NULL"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoHMM_-7-INVALID_ERR_SEV
SEVERITY: InformationFORMAT: "Invalid HMM error severity (%d) obtained"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An invalid error severity was obtained by hmm due to which a correct error severity will not be reflected."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoHMM_-7-INVALID_CTC_EVE
SEVERITY: InformationFORMAT: "HMM INFO Received an event(%d) not registered for."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The HMM received an unexpected event, default action"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoHMM_-7-CTC_EVENT_INFO
SEVERITY: InformationFORMAT: "HMM CTC EVENT HNDLR Ctc event %s Received"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "CTC EVENT HANDLER, TRACE"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoHMM_-1-IPC_CHAN_FAIL
SEVERITY: FatalFORMAT: "HMM IPC CHANNEL FAILURE Detected by module = %s , Errno = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "IPC CHANNEL FAILED, CANNOT PROCEED FURTHER"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoHMM_-1-CTC_EVT_REG_FAI
SEVERITY: FatalFORMAT: "CTC Registration for event %s failed."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Events needed for sheld card availability bitmap."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoHMM_-1-DEVICE_INIT_FAI
SEVERITY: FatalFORMAT: "HMM Initialiazation routine %s failed for device %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The HMM_HW_DEVICE initialization failed, CANNOT PROCEED FURTHER"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoHMM_-1-CTC_APP_INIT_FA
SEVERITY: FatalFORMAT: "HMM ctcAppInitDoneConfirm() Failed with errno = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Hmm Cannot proceed further, ctc failure detected"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoHMM_-1-HMM_MALLOC_FAIL
SEVERITY: FatalFORMAT: "HMM module = %s, failed to allocate memory"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Device ID value is wrong, CANNOT PROCEED FURTHER"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoHMM_-7-DEV_EVENT_FAIL
SEVERITY: InformationFORMAT: "HMM DEVICE EVENT FAILURE DETECTED Return Value = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "hmmProcDeviceEvent Module failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoHMM_-7-ERR_STATE_CHANG
SEVERITY: InformationFORMAT: "HMM DEV ERROR STATE %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Change in the state of the error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required Info