MGX and SES Error Messages, Release 4
MGX and SES Error Messages, Release 4.0.10 (part D)
-
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
Error Messages for Release 4.0.10
MESSAGE: DDLXIFDEV_CRDMP_EVENT
MESSAGE: DDLSCHEDDEV_CRDMP_EVENT
MESSAGE: DDLQUEUEDEV_CRDMP_EVENT
MESSAGE: DDLPORTDEV_CRDMP_EVENT
MESSAGE: DDLPIFDEV_CRDMP_EVENT
MESSAGE: DDLFRAMER_CRDMP_EVENT
MESSAGE: MAKE_HSB_ACTIVE_FAILED
DDTS: "control-point/pxm-connmgm"
MESSAGE: CUTS_NON_DIR_FILE_FOUND
MESSAGE: FILE_STATE_GENERATING
MESSAGE: MAKE_HSB_ACTIVE_FAILED
MESSAGE: DUPLICATE_CONNID_EXISTS
Error Messages for Release 4.0.10
The following error messages were added for Release 4.0.10.
DDTS: "drivers"
MESSAGE: DRV_EVENT
SEVERITY: InformationFORMAT: "DDL_EVENT: %s\n"FLAG: Write BramLIMIT: 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 infoMESSAGE: DDLXIFDEV_CRDMP_EVENT
SEVERITY: InformationFORMAT: "DDLXIFDEV_CRDMP_EVENT: %s 0x%x 0x%x\n"FLAG: Write BramLIMIT: One TickEXPLANATION: "DDLXIFDEV Core Dump 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 infoMESSAGE: DDLSCHEDDEV_CRDMP_EVENT
SEVERITY: InformationFORMAT: "DDLSCHEDDEV_CRDMP_EVENT: %s 0x%x 0x%x\n"FLAG: Write BramLIMIT: One TickEXPLANATION: "DDLSCHEDDEV Core Dump 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 infoMESSAGE: DDLQUEUEDEV_CRDMP_EVENT
SEVERITY: InformationFORMAT: "DDLQUEUEDEV_CRDMP_EVENT: %s 0x%x 0x%x\n"FLAG: Write BramLIMIT: One TickEXPLANATION: "DDLQUEUEDEV Core Dump 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 infoMESSAGE: DDLPORTDEV_CRDMP_EVENT
SEVERITY: InformationFORMAT: "DDLPORTDEV_CRDMP_EVENT: %s 0x%x 0x%x\n"FLAG: Write BramLIMIT: One TickEXPLANATION: "DDLPORTDEV Core Dump 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 infoMESSAGE: DDLPIFDEV_CRDMP_EVENT
SEVERITY: InformationFORMAT: "DDLPIFDEV_CRDMP_EVENT: %s 0x%x 0x%x\n"FLAG: Write BramLIMIT: One TickEXPLANATION: "DDLPIFDEV Core Dump 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 infoMESSAGE: DDLFRAMER_CRDMP_EVENT
SEVERITY: InformationFORMAT: "DDLFRAMER_CRDMP_EVENT: %s 0x%x 0x%x\n"FLAG: Write BramLIMIT: One TickEXPLANATION: "DDLFRAMER Core Dump 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 "config-upload"
MESSAGE: CUT_RAM_FILE
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cutram) Ftp Request for File:%s Physical Slot Number Failed."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Unable to determine the Physical Slot Number for the file."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUT_RAM_NAME
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x) (cutram) Ftp Request for File:%s Ram disk name Failed."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Unable to determine the Ram disk name for the file."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUT_RAM_LOG
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x) (cutram) Ftp Request for File:%s Logical Slot:%d Phy Slot Conv Failed."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Unable to convert the Logical Slot to a Physical Slot Number."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "shm"
MESSAGE: CBC_HMM_ERR
SEVERITY: ErrorFORMAT: "%s cbc_num = %d,%d,%d,%d : %s"FLAG: No FlagLIMIT: One TickEXPLANATION: "CBC HMM Event."RECOMMENDED Action: Please capture the following information and call your Cisco technical support representative:REQUIRED_INFO: " On PXM:1. dspcds2. dsplog -sl <slot that experienced the error>3. dsplog -sl <other pxm slot>4. dsperr for slots specified above.5. dspcbclk "DDTS: "control-point"
MESSAGE: SEMCREATE_FAILED
SEVERITY: WarningFORMAT: "%d: errno 0x%x Semaphore create failed for %s."FLAG: No FlagLIMIT: One TickEXPLANATION: "Can not create semaphore that is required to protect MIB functions"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEMTAKE_FAILED
SEVERITY: WarningFORMAT: "%d: errno 0x%x Semaphore take failed for %s."FLAG: Stack TraceLIMIT: One TickEXPLANATION: "Can not take semaphore that is required to protect MIB functions"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEMGIVE_FAILED
SEVERITY: WarningFORMAT: "%d: errno 0x%x Semaphore give failed for %s."FLAG: Stack TraceLIMIT: One TickEXPLANATION: "Can not release semaphore which required to protect MIB functions"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEMTAKE_TASK
SEVERITY: WarningFORMAT: "%d: errno 0x%x Semaphore was taken by taskId 0x%x, taskName %s."FLAG: Stack TraceLIMIT: One TickEXPLANATION: "Cannot take semaphore because another task has it"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEMTAKE_RECOVER
SEVERITY: WarningFORMAT: "%s_%d: Could not recover Semaphore from Task Id %x, Task Name %s."FLAG: Stack TraceLIMIT: One TickEXPLANATION: "A time out has occured and the previous task still has the semaphore"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "pxm-connmgm"
MESSAGE: RAMSYNCEV
SEVERITY: WarningFORMAT: "Line %d: Ram Sync %s error - errno = 0x%x, resetCause = %d"FLAG: No FlagLIMIT: One SecondEXPLANATION: "Ram sync related problems/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 support:1) 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 requiredDDTS: "pxm-connmgm"
MESSAGE: CNF_MISMATCH
SEVERITY: Major AlertFORMAT: "Slot %d, PS card %d Line %d : %s"FLAG: No FlagLIMIT: One TickEXPLANATION: "Config mismatch between SHM and Autocard"RECOMMENDED ACTION: "Collect information specified in REQUIRED_INFO: field and call TAC"REQUIRED_INFO: "Collect dsplog, dsperr information"MESSAGE: INFO_LOG
SEVERITY: InformationFORMAT: "Info Log %s Slot %d Data %d line %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Informational Log"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "drivers"
MESSAGE: GENERROR
SEVERITY: WarningFORMAT: "Gen Error : %s: errno = 0x%x Args : %d %d %d %d"FLAG: No FlagLIMIT: Four HoursEXPLANATION: "Event logs for general errors in Rx direction"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: A2SARSNDERROR
SEVERITY: WarningFORMAT: "P1 SAR send error: status %x, errno %x"FLAG: No FlagLIMIT: One SecondEXPLANATION: "This means the atmizerSarFrameSend has failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: "Capture the followinga. SarShowQPtrs from shellconnb. SarShow from shellconnIf status in the event log is 4, please capture SarLcnShow <errno>"MESSAGE: INVMAGIC
SEVERITY: ErrorFORMAT: "QE#%d InvCnt=%d Sts=0x%x #Frms=%d HCnt=%d SCnt=%d Flgs=0x%x InQ=%d CPUdump=%s"FLAG: No FlagLIMIT: One TickEXPLANATION: "The special magic field in the given message header is not a valid one. This indicates that QE cannot transmit the SAR messages in a specified interval. The retransmission will be started. The following are displayed:a) InvCnt - count of invalid magic condition.b) Sts - value of QE status register.c) #Frms - number of frames in QE xmt queue.d) HCnt - Hang counter of QE sar task.e) SCnt - Starvation counter of QE sar task.f) Flgs - QE scheduler flag.g) InQ - 1 if frm already in queue, 0 if noth) CPU dump - index of CPU dump if one taken. "RECOMMENDED ACTION: No action requiredREQUIRED_INFO: " a) dsplog -mod SAR on PXMb) dsplog -mod SAR2 on PXMc) sarQe1210CpuDumpHelp from shellconnd) sarQe1210ShowCpuDump from shellconne) sarQe1210DisplayCpuDump from shellconnf) sarQe1210StatsShow 0 from shellconng) sarQe1210StatsShow 1 from shellconn "DDTS: "shm"
MESSAGE: CD_INFO
SEVERITY: InformationFORMAT: "Slot %d ,%s"FLAG: No FlagLIMIT: One TickEXPLANATION: "HSB info for the specific slot"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoMESSAGE: MIB_MISMATCH
SEVERITY: WarningFORMAT: "Prislot %d Mib ver %d, SecSlot %d Mib ver %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "HSB MIB version mismatch between pri and sec slot"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoMESSAGE: CD_NOT_READY
SEVERITY: WarningFORMAT: "Slot %d, not ready to go Active"FLAG: No FlagLIMIT: One TickEXPLANATION: "Slot is not hotstandby yet so cannot go active"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoMESSAGE: MAKE_HSB_ACTIVE_FAILED
SEVERITY: WarningFORMAT: "%s, Slot %d, Redundant slot %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Error in making HSB go Active"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoDDTS: "atmsig"
MESSAGE: FAILHALFLEGREM
SEVERITY: NoticeFORMAT: "halfLeg removal failed, %s"FLAG: No FlagLIMIT: One TickEXPLANATION: "Failed to remove endpoint connection resources."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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 PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.DDTS: "control-point"
MESSAGE: FM_OPEN_FAIL
SEVERITY: ErrorFORMAT: "%s: slotNum: %d, reqType : %d, Msg: %s"FLAG: No FlagLIMIT: 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, dsplogDDTS: "pnnisys"
MESSAGE: CCB_INVALID_VALUE
SEVERITY: ErrorFORMAT: "%s= %d - %s"FLAG: Stack TraceLIMIT: One TickEXPLANATION: "Detect module-id value goes beyond the MODULE_MAX "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: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.DDTS: "drivers"
MESSAGE: SAR_PURGE_QUEUES
SEVERITY: ErrorFORMAT: "QE1210 Purge Frm & Notify Q. QE: %d Reason: %s "FLAG: Stack TraceLIMIT: No ThrottlingEXPLANATION: "QE1210 Notify Q may be out of sync. with frames in SAR MbinIn this case, Rx Fifo, Notify Q and SAR Mbin queues must be purged"RECOMMENDED ACTION: "if QE1210 out of sync. can not be resolved by purging the queues, then card reset need to be done"REQUIRED_INFO: "Pls goto shell of the controller cards and collect the infor. using shell command -- sarQe1210IsrShow 0"MESSAGE: GEN_INFO
SEVERITY: InformationFORMAT: "%s() failed: errno:0x%x, callerPC:0x%x"FLAG: No FlagLIMIT: One MinuteEXPLANATION: "Logging gen info"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: ALARM_SET
SEVERITY: Major AlertFORMAT: "SAR Alarm Set: %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "This log event indicates a SAR alarm has occurred."RECOMMENDED ACTION: No action requiredREQUIRED_INFO: " a) dspsaralms on PXM to determine slotb) dspsaralms <almType> <slot> on PXMc) dspsaralms <almType> <slot> <almId> on PXMd) sarQe1210StatsShow 0 from shellconne) sarQe1210StatsShow 1 from shellconn "MESSAGE: ALARM_CLR
SEVERITY: Minor AlertFORMAT: "SAR Alarm Clr: %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "This log event indicates a SAR alarm has cleared."RECOMMENDED ACTION: No action requiredREQUIRED_INFO: " a) dspsaralms on PXM to determine slotb) dspsaralms <almType> <slot> on PXMc) dspsaralms <almType> <slot> <almId> on PXMd) sarQe1210StatsShow 0 from shellconne) sarQe1210StatsShow 1 from shellconn "MESSAGE: ALARM_ERROR
SEVERITY: ErrorFORMAT: "SAR Alarm Error: %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "This log event indicates an error occurred in SAR alarm processing."RECOMMENDED ACTION: No action requiredREQUIRED_INFO: " a) dsplog -mod SAR on PXMb) dspsaralms on PXM to determine slotc) dspsaralms <almType> <slot> on PXMd) dspsaralms <almType> <slot> <almId> on PXMe) sarQe1210StatsShow 0 from shellconnf) sarQe1210StatsShow 1 from shellconn "MESSAGE: SAR_HDR_ERR
SEVERITY: ErrorFORMAT: "SAR HDR Err. line: %d QE: %d hdrPtr: %x bufPtr: %x offset: %d len: %d glcn: %x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "QE1210 INJ frozen. Card reset needed for recovery"RECOMMENDED ACTION: "The card will be reset if QE1210 INJ frozen is more than 20 seconds. After the cared is reset, we should check the log. Msg."REQUIRED_INFO: "This should not continuously happen. if the pxm45 resets continuously, collect dsplog, dsperr, dspver, etc and call TAC"MESSAGE: SAR_QUE_CORRUPT
SEVERITY: ErrorFORMAT: "SAR Rx Queue Corruped. line: %d QE: %d rdPtr: %x wrPtr: %x nextPtr: %x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "This log. event indicates that SAR Rx Queueis corrupted."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: "dsplog -mod SAR on both active and stdby pxm cards."MESSAGE: SAR_OVFLW_START
SEVERITY: WarningFORMAT: "SAR overflow start in QE: %d Idle2OvflwCnt: %d"FLAG: Write BramLIMIT: One TickEXPLANATION: "SAR overflow has occurred in QE. The overflow will be detected and be shut down if this overflow lasts for more than 15 seconds (i.e. sustaining overflow)"RECOMMENDED ACTION: "reenable the disabled SAR conn which caused the SAR overflow, if needed."REQUIRED_INFO: " a) dsplog -mod SAR2 on PXMb) dspsaralms on PXM to determine slotc) dspsaralms <almType> <slot> on PXMd) dspsaralms <almType> <slot> <almId> on PXMe) sarQe1210StatsShow 0 from shellconnf) sarQe1210StatsShow 1 from shellconn "MESSAGE: SAR_OVFLW_END
SEVERITY: WarningFORMAT: "SAR overflow end in QE: %d dsbGlcnFrm#: %d ovflwType: %s"FLAG: Write BramLIMIT: One TickEXPLANATION: "SAR overflow has occurred in QE. The overflow will be detected and be shut down if this overflow lasts for more than 15 seconds (i.e. sustaining overflow)"RECOMMENDED ACTION: "reenable the disabled SAR conn which caused the SAR overflow, if needed."REQUIRED_INFO: " a) dsplog -mod SAR2 on PXMb) dspsaralms on PXM to determine slotc) dspsaralms <almType> <slot> on PXMd) dspsaralms <almType> <slot> <almId> on PXMe) sarQe1210StatsShow 0 from shellconnf) sarQe1210StatsShow 1 from shellconn "MESSAGE: SAR_INJFRZN_ERR
SEVERITY: ErrorFORMAT: "ln: %d QE: %d Sts3: %x tName: %s Hed1: %x Hed2: %x DmaSrc: %x DmaLen: %x pyldLen: %x hold: %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "QE1210 INJ frozen. Card reset needed for recovery"RECOMMENDED ACTION: "The card will be reset if QE1210 INJ frozen is more than 20 seconds. After the cared is reset, we should check the log. Msg."REQUIRED_INFO: "This should not continuously happen. if the pxm45 resets continuously, collect dsplog, dsperr, dspver, etc and call TAC"MESSAGE: SAR_RESET_QE
SEVERITY: ErrorFORMAT: "Reset QE : QE=%d, Rsn=%s, sts0=%x, sts1=%x, sts2=%x, sts3=%x, RstCnt=%d, Cnt1=%d, Cnt2=%x"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "When a QE fatal error such as Free List Empty occurs, we must reset QE chip. During the QE reset, all of incoming cells will be discarded. QE can be recovered after the reset."RECOMMENDED ACTION: No action requiredREQUIRED_INFO: "Please use dsplog -mod SAR to collect the info. when this problem happens."DDTS: "atmsig"
MESSAGE: FAILHALFLEGREM
SEVERITY: NoticeFORMAT: "halfLeg removal failed, %s"FLAG: No FlagLIMIT: Five SecondsEXPLANATION: "Error in freeing up data structure"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.DDTS: "snmp-ma"
MESSAGE: NOENTITYFOUND
SEVERITY: InformationFORMAT: "%s: No Entity found in the system. errno = 0x%x"FLAG: Stack TraceLIMIT: One TickEXPLANATION: "could not create entries in entPhysicalTable"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "control-point/pxm-connmgm"
MESSAGE: FOPEN_FAILED
SEVERITY: WarningFORMAT: "%s: slotNum %d, fileType : %d, Msg: %s"FLAG: No FlagLIMIT: 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 infoMESSAGE: FREAD_FAILED
SEVERITY: WarningFORMAT: "%s: fD: %d, slotNo: %d, fileType: %d, Msg: %s"FLAG: No FlagLIMIT: 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 infoMESSAGE: FWRITE_FAILED
SEVERITY: WarningFORMAT: "%s: fD: %d, slotNo: %d, fileType: %d, Msg: %s"FLAG: No FlagLIMIT: 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 infoDDTS: "axsme_apps"
MESSAGE: EM_ERROR
SEVERITY: ErrorFORMAT: "EM ERROR: %s\n"FLAG: Stack TraceLIMIT: 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) "DDTS: "atmsig"
MESSAGE: DISABLE_PORT
SEVERITY: WarningFORMAT: "NCDP being downed on port %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "NCDP being downed on port because we could not latch on to clock signal"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "shm"
MESSAGE: PXM_PATH_FAIL
SEVERITY: Major AlertFORMAT: "Communication Path error with Active PXM in slot: %d, %s, MaxPollRetry: %d, MaxPollMiss: %d, MonFromStby: %d"FLAG: Write BramLIMIT: One TickEXPLANATION: "The Active PXM is not sending Polls, declaring the card as frozen"RECOMMENDED ACTION: "Verify if the Old Active PXM went through a ful reset and came up fine. If it does not come up replace the PXM"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.MESSAGE: DBG_FILE_WR
SEVERITY: InformationFORMAT: "Saving the SCM Poll failure debug info for slot: %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The Service module is not responding to the Poll Request, so collecting the path data and saving it in a file"RECOMMENDED ACTION: No action requiredREQUIRED_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.MESSAGE: DBG_FILE_ERR
SEVERITY: ErrorFORMAT: ":%s: Failed for Poll Failure Debug File for slot: %d, errno: 0x%x"FLAG: No FlagLIMIT: One TickEXPLANATION: "File operation failed for the Poll failure debug file on the specified slot"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.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.MESSAGE: DBG_DIR_ERR
SEVERITY: ErrorFORMAT: ":%s: failed for Poll Failure Debug Directory, errno: 0x%x"FLAG: No FlagLIMIT: One TickEXPLANATION: "IO operation failed for Directory for storing the Poll failure debug information"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.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 representativeDDTS: "pxm-connmgm"
MESSAGE: SYNCRAMERR
SEVERITY: Major AlertFORMAT: "%s: Sync Ram Error at line %d : errno %x"FLAG: No FlagLIMIT: One SecondEXPLANATION: "This error indicates a general error in sync ram area"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 support:1) 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 requiredMESSAGE: SYNCRAMEV
SEVERITY: WarningFORMAT: "Sync Ram Error at line %di, errno = 0x%x"FLAG: No FlagLIMIT: One SecondEXPLANATION: "This error indicates a general error in sync ram area"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 support:1) 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 requiredDDTS: "hw-poll"
MESSAGE: INV_DEVICE_PTR
SEVERITY: InformationFOMAT "Invalid device pointer in poll Q, device = %p, devId %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "An invalid pointer was detected in the HMM polling queue"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CORRUPT_POLL_Q
SEVERITY: InformationFORMAT: "HMM Poll Q corrupted (devId = %d, devPtr=%p): %s"FLAG: No FlagLIMIT: One TickEXPLANATION: "Corrupt HMM Poll Queue."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: DISK_PARMS_CHG
SEVERITY: InformationFORMAT: "Disk Spin Parms Changed (SpinEnabled: NoAccess, SpinDown, Start Time:) From: %d, %d, %d, %d:%d:%d TO: %d, %d, %d, %d:%d:%d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The Disk Spin Down and Up has been done successfully"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: DISK_SPIN_OK
SEVERITY: InformationFORMAT: "Disk Spin Down complete: NoAccess Time: %d, SpinDown Time: %d, Start Time: %d:%d:%d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The Disk Spin Down and Up has been done successfully"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: DISK_SPIN_NOK
SEVERITY: InformationFORMAT: "Disk Spin Down Not complete: Time: NoAccess: %d, SpinDown: %d, Start: %d:%d:%d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The Disk Spin Down and Up has NOt been done successfully"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: DISK_SPIN_STATS
SEVERITY: InformationFORMAT: "Disk Spin Stats: Spin Done: %d, Not Done: %d, InAct Retry(total): %d (%d), Spin Retry(total): %d(%d), Time Done: %d:%d:%d."FLAG: No FlagLIMIT: One TickEXPLANATION: "The Disk Spin Down/Up stats collected log"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: DISK_SPIN_ERR
SEVERITY: ErrorFORMAT: "Disk Spin %s Failed, errno = 0x%x"FLAG: No FlagLIMIT: One TickEXPLANATION: "The Disk Spin Down/Up 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: 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.MESSAGE: DISK_TMR_ERR
SEVERITY: ErrorFORMAT: "Failed to Start the timer for Spin Down Handler, errno: %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Failed to start the timer for spinning down/up the hard disk"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.MESSAGE: BRAM_ENBL_FAIL
SEVERITY: Major AlertFORMAT: "HMM:Bram write enable failed. Expected value:0x%02x Actual value:0x%02x"FLAG: No FlagLIMIT: One TickEXPLANATION: "Write Enable for BRAM failed. This means that that the PIO controlling the writes to BRAM/ BRAM itself is not functioning properly and any further writes to BRAM will not be effective Card will go to failed state. In a redundant configuration this will cause a switchover "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 support:1) 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 requiredDDTS: "sctfm"
MESSAGE:DIRECTORY_DELETE
SEVERITY: InformationFORMAT: " directory %s deleted"FLAG: No FlagLIMIT: One SecondEXPLANATION: "This is just for information, telling us that the specified directory has been deleted from PXM HDD"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.MESSAGE: SYNCRAMERR
SEVERITY: InformationFORMAT: "Sync Ram Error line %d cause %s errno %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Internal Error. Could occur under normal circumstances. Typical scenario includes reset of standby PXM while bulk/incrementa sync is in progress"RECOMMENDED ACTION: "There may not be a need for any corrective action as the card would be reset. However please collect the following information dspscts on both active and standby PXM If you find they are different data then for further analysis and call TAC"REQUIRED_INFO: No required infoDDTS : pxm-connmgm
MESSAGE: RAMSYNCEV
SEVERITY: WarningFORMAT: "Line %d: PXMCM Ram Sync %s error - errno = 0x%x, resetCause = %d"FLAG: No FlagLIMIT: One SecondEXPLANATION: "This error is logged while updating the standby PXM, Standby card is rebooted"RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team./REQUIRED_INFO : Please capture the following information from the PXM45 cli and call your TAC support:1 ) 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 requiredMESSAGE: CREF_NOT_FOUND
SEVERITY: WarningFORMAT: "%s: ConnRef not found for lin = %d, vpi = %d, vci = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The connection endpoint does not exist for the given lin, vpi, vci"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 support:1) 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 requiredMESSAGE: PARTN_BW_EXCEED
SEVERITY: WarningFORMAT: "line %d: Partition B/W exceeded for lin %d part %d cos %d B/W1 = %d, B/W2 = %d, B/W3 = %d, B/W4 = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The partition b/w exceeds the required b/w for connection commit"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 support:1) 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 requiredMESSAGE: VI_BW_EXCEED
SEVERITY: WarningFORMAT: "line %d: VIs B/W exceeded for lin %d part %d cos %d B/W1 = %d, B/W2 = %d , B/W3 = %d, B/W4 = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The VI b/w exceeds the required b/w for connection commit"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 support:1) 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 requiredMESSAGE: SLOT_BW_EXCEED
SEVERITY: WarningFORMAT: "line %d: Slot B/W exceeded for lin %d part %d cos %d B/W = %d, Max B/W = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The slot b/w exceeds the required b/w for connection commit"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 support:1) 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 requiredMESSAGE: BW_CAC_FAIL
SEVERITY: WarningFORMAT: "line %d: Error in b/w cac for lin = %d, part =%d, cos = %d, ingr ecr =%d, egr ecr =%d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Bandwidth CACing failed for the given connection endpoint"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 support:1) 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 requiredMESSAGE: RSRC_ALLOC_FAIL
SEVERITY: WarningFORMAT: "line %d: Resource Check/Alloc Failed for lin %d vpi %d vci %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Resource Allocation failed for a given connection endpoint"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 support:1) 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 requiredMESSAGE: CREF_LIMIT:_REACHED
SEVERITY: WarningFORMAT: "line %d: cref limit reached on qe %d lin %d partId %d curr %d cmtted %d max %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Cref allocation failed for the connection"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 support:1) 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 requiredMESSAGE: LCN_LIMIT:_REACHED
SEVERITY: WarningFORMAT: "line %d: LCN limit reached for lin %d part %d cos %d value1 %d value2 %d value3 %d value4 %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "LCN limit reached for the given interface"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 support:1) 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 requiredMESSAGE: INTF_CFG_ERR
SEVERITY: WarningFORMAT: "line %d: %s : lin %d arg1 = %d arg2 = %d arg3 = %d arg4 = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Configuration failed for the given interface"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 support:1) 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 requiredMESSAGE: PART_CFG_ERR
SEVERITY: WarningFORMAT: "line %d: %s : lin %d part %d arg1 = %d arg2 = %d arg3 = %d arg4 = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Configuration failed for the given partition"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 support:1) 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 requiredMESSAGE: IF_PLCY_CFG_ERR
SEVERITY: WarningFORMAT: "line %d: %s : lin %d part %d arg1 = %d arg2 = %d arg3 = %d arg4 = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Interface Policy configuration failed for the given partition"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 support:1) 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 requiredMESSAGE: VPI_VCI_RANGE_ERR
SEVERITY: WarningFORMAT: "line %d: %s : lin %d part %d arg1 = %d arg2 = %d arg3 = %d arg4 = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Incorrect VPI/VCI range"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 support:1) 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 requiredDDTS: "snmp-ma"
MESSAGE: SEM
SEVERITY: WarningFORMAT: "%d: caller 0x%x, errno 0x%x, %s"FLAG: Stack TraceLIMIT: One TickEXPLANATION: "Master agent semaphore events."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "CLI"
MESSAGE: SCM_PARMS_CNF
SEVERITY: InformationFORMAT: "Attempt to change SCM Poll Parms:Max Poll Retry: %d, Max Miss Poll: %d, Mon From Stby: %d."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "User is changing the SCM poll parms"RECOMMENDED ACTION: No action requiredREQUIRED_INFO: No required infoDDTS: "config-upload"
MESSAGE: CUTS_DIR_FOUND
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) Directory %s found, No need to create"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "CUTS found directory"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_NON_DIR_FILE_FOUND
SEVERITY: ErrorFORMAT: "(L %d:errno 0x%x)(cuts) found a non directory entry of name %s found."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "CUTS found a non directory entry of name CUT. Please remove this file and create a directory C:/CUT instead. Otherwise, Config Upload will fail."RECOMMENDED ACTION: Make sure the C:/CUT is a directory and not a file name. If it is a file name, remove the file and create C:/CUT directory. If the card is active, try to copy a file into that C:/CUT directory. If the operation is not sucessfull, contact TAC.REQUIRED_INFO: If CLI available, capture the following command output before contact TAC:1) dir "C:"2) dspversion3) dspdate4) dsplog -mod CUTSMESSAGE: CUTS_IOCTL_FAILED
SEVERITY: ErrorFORMAT: "(L %d:errno 0x%x)(cuts) Can not get stats for %s "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Scheduler task is not able to determine whether C:/CUT is a directory or a file. Config Upload will fail if C:/CUT directory does not exist. "RECOMMENDED ACTION: Make sure the C:/CUT is a directory and not a file name. If it is a file name, remove the file and create C:/CUT directory. If the card is active, try to copy a file into that C:/CUT directory. If the operation is not sucessfull, contact TAC.REQUIRED_INFO: If CLI available, capture the following command output before contact TAC:1) dir "C:"2) dspversion3) dspdate4) dsplog -mod CUTSMESSAGE: CUTS_OPEN_FAILED
SEVERITY: ErrorFORMAT: "(L %d:errno 0x%x)(cuts) unable to open dir/file %s "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Scheduler task is not able to open C: drive. This cause C:/CUT directory not being able to create. Config Upload will fail."RECOMMENDED ACTION: Make sure the C:/CUT is a directory and not a file name. If it is a file name, remove the file and create C:/CUT directory. If the card is active, try to copy a file into that C:/CUT directory. If the operation is not sucessfull, contact TAC.REQUIRED_INFO: If CLI available, capture the following command output before contact TAC:1) dir "C:"2) dspversion3) dspdate4) dsplog -mod CUTSMESSAGE: CUTS_MKDIR_FAILED
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) unable to create directory %s "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Scheduler Task is unable to create a directory. Config Upload will fail if C:/CUT directory does not exist. "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoTAC_DETAILS: No TAC DetailsMESSAGE: ACK_TIMEOUT
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) ACK timeout, task status=\"%s\", index=%d, file type=%d, threshold=%d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Scheduler task timeout while waiting acknowlegdemeent from worker task"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_EPID
SEVERITY: ErrorFORMAT: "(L %d:errno 0x%x)(cuts) Creation of CUTS EPID \"%s\" failed rc = 0x%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "Failed to create epid for cuts. This might result in Config Upload not able to function correctly."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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTS_TIMER_CREATE
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) Creation of timer failed rc= 0x%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "Timer Creation failed. This might result in Config Upload not able to function correctly."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 : If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsploMESSAGE: CUTS_ATTHDLR
SEVERITY: ErrorFORMAT: "(L %d:errno 0x%x)(cuts) Attaching of handler \"%s\" failed Epid = 0x%08X rc= 0x%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "Attaching of handler to a cuts epid has failed. The epid name, number and error code are listed. This might result in Config Upload not able to function correctly"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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTS_TMR_SCHD
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) failed to schedule timer in \"%s\" timeout value = %d, timer type = %d, rc= 0x0%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "failed to schedule timeout. This might cause a request for Config Upload to be drop."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_TMR_CNCL
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) failed to cancel timer in \"%s\" timer type = %d, rc= 0x0%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "failed to cancel timer"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoTAC_DETAILS: No TAC DetailsMESSAGE: CUTS_IPC_FREE_ERR
SEVERITY: ErrorFORMAT: "(L %d:errno 0x%x)(cuts) IPC Message Free Failed : rc = 0x%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "Error in Freeing IPC message. Potential memory leak."RECOMMENDED ACTION: If this event shows up exessively(about 5 or more times) in the event log, please log a bug and contact TAC immediatly. This is a potentential memory leak.REQUIRED_INFO: If CLI available, capture the following command output before contacting TAC:1) dspversion2) dspdate3) dspmempart 2 14) dsplog -mod CUTS5) dsplog -mod CUTWRKRMESSAGE: IPCFAIL
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) IPC SEND FAILED TO \"%s\" from \"%s\" request:%d"FLAG: No FlagLIMIT: One TickEXPLANATION: "IPC send failed. This will result in Config Upload file creation request being dropped."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: IPC_ALLC_FAILED
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) failed to allocate ipc buffer in \"%s\"."FLAG: No FlagLIMIT: One TickEXPLANATION: "failed to allocate ipc buffer. This will result in Config Upload file creation request being dropped."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_INVALID_RQ
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) Invalid request received by cuts from system epid: req = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Invalid request received by Scheduler task(CUTS)"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_INVLD_RQSTATE
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) Request received by cuts while in invalid state, rq ignored: state = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Request sent to cuts while cuts in invalid state"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_WRKR_UPDAT
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) failed to update the worker task of index (%d) to state %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "CUTS unable to update worker task state. This might cause the death of the worker task"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TMR_ERROR
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) failed to find a worker for expired timerID = %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "CUTS timer expired with no associated worker task found"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RNWY_TASK
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts)found a worker task(%d)\"%s\" RUNNING yet not working on any file"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "CUTS timer expired, found a task in running with no work"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BAD_RSPNSE
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) invalid epid in an epid response or child active message from 0x%08X."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "CUTS received a bad epid_response or child active msg"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_FC_FAILED
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) failed to process file creation request: %s for file 0x%08X."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts failed to service file creation request"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BAD_FILEINDX
SEVERITY: ErrorFORMAT: "(L %d:errno 0x%x)(cuts) Invalid File index found in \"%s\" file Index = %d."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts found an invalid file index. This might cause Config Upload file creation to fail. "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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: FILE_STATE_GENERATING
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts)request made to generate an already generating file ignored:fileIndex = %d."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts got a request to generate a file already being generated"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_CHILD_ACTIVE
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) rcvd a child active message from taskid: %d, taskname:%s."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts got a child active message from a task"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_EPID_RESPONSE
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) %s task is registered with Scheduler task as taskid: %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts got an EPID response message from a task"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_FC_DONE
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) rcvd file creation done from taskid: %d, file:%d "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts got a file creation done from task"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_TRAP_NOTASK
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x)(cuts) sent TRAP cwBulkNoTaskAvailable(60904) for file:%d "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts sent trap to CWM 60904"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_TRAP_START
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) sent TRAP cwBulkFileCreationStarted(60901) for file:%d "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts sent trap to CWM 60901"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_TRAP_FAIL
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) sent TRAP cwBulkFileCreationFailed(60905) for file:%d "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts sent trap to CWM 60905 which signals file creation failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_TRAP_DONE
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) sent TRAP cwBulkFileCreationDone(60902) for file:%d "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts sent trap to CWM 60902"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_TRAP_ABRT
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) sent TRAP cwBulkFileCreationAborted(60903) for file:%d "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cuts sent trap to CWM 60903"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_UPDT_DONE
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)API to update %s for filetype %d done"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Update to FCB and mibs for filetype specified done"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEND_CUTV_FAIL
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)Failed to send %s message for filetype %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "API to send message to the CUTV task failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: UPD_FCB_FAIL
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x) Failed to update FCB"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "API to update the FCB returned ERROR"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TMR_REINIT_FAIL
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x) Failed to reinit timer with reason %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to reinitiate timers"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEMGIVE_FAIL
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x) could not give up sem %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "semgive for sem failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_FILE_MUTEX
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)(cuts) FileIndex %d cannot be be createdsince another CONN/STATIC-CONN file is being created "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Config upload should not create both conn and conn-update files together. If there is another conn/conn-update file running, the request will be rejected"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TXID_GET_FAILED
SEVERITY: WarningFORMAT: "(L %d:errno 0x%x) Config upload failed to receive a valid TxId from the card"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Config upload failed to receive a valid TxId from the card"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: INV_TXID
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x) fileType = %d, card TxID= %d less than req TxID = %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "The requested TxID is greater than the card TxID"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CANNOT_PROCEED
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x) fileType = %d, reqType= %d,reqTxID= %d: cutwCanCreationProceed returned FALSE"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Either due to mutual exclusion or the reqTxID being greater than the card TxID, cfgupload cannot continue"RECMMENDED_ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TRAP_SEND_FAIL
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x) Trap not sent by %s for file:%d "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "API to send trap failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTS_UPDT_FAIL
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x)API to update %s returned error for filetype %d "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Update to FCB and mibs for filetype specified failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RMTCLOSE_FAIL
SEVERITY: InformationFORMAT: "(L %d:errno 0x%x) ssiRmtFileClose fails"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "ssiremoteclose API returned error"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "signaling"
MESSAGE: CC_AUD_REL
SEVERITY: WarningFORMAT: "CC Func:%s; logItf:%ld;callRef:%ld,endptRef:%d\n"FLAG: No FlagLIMIT: One TickEXPLANATION: "Audit to release the call"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:a) General: dspver, depcds, dsplog, dsperr, dspmempartb) Interface: dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,c) Connection: dsppncons, dspcons, dspsigstats, dsppnctlvc,d) Congestion: dsppnportcc, dspsvcparm,e) Topology: dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.DDTS: "clocking"
MESSAGE: CLK_IPC_FAIL
SEVERITY: Major AlertFORMAT: "CLK IPC CHANNEL FAILURE: Detected by module = %s, errno = 0x%x"FLAG: No FlagLIMIT: One TickEXPLANATION: "IPC Channel Failed, Clock Functionality may be affected"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, dspver, dsperr, dspclkalms before calling the Cisco Techincal support representative.MESSAGE: EPID_RESOLVE_FAILED
SEVERITY: Major AlertFORMAT: "%s CLK TASK EPID INVALID"FLAG: No FlagLIMIT: One TickEXPLANATION: "ACTIVE CLK TASK CAN NOT RESOLVE STBY EPID, CLOCK UPDATES NOT SEND"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, dspver, dsperr, dspclkalms before calling the Cisco Techincal support representative.MESSAGE: TIMER_SCHEDULE_FAIL
SEVERITY: WarningFORMAT: "Attempt to schedule %s timer failed. Reason: %s"FLAG: No FlagLIMIT: One TickEXPLANATION: "Clock Manager Timer could not be scheduled."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, dspver, dsperr, dspclkalms before calling the Cisco Techincal support representative.MESSAGE: TIMER_CANCEL_FAIL
SEVERITY: WarningFORMAT: "Attempt to cancel %s timer failed. Reason: %s"FLAG: No FlagLIMIT: One TickEXPLANATION: "Clock Manager Timer could not be cancelled."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, dspver, dsperr, dspclkalms before calling the Cisco Techincal support representative.DDTS: "rpm"
MESSAGE: DB_ALLOC_ERR
SEVERITY: Major AlertFORMAT: "%s %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "This is an error logged when not able to allocate RVT database for RPM-PR card in the shelf. This will impact the provisioning on the RPM-PR for which the error is logged."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 and contact your technical support representative.a) dspcdsb) dspcdc) dsperrd) dsploge) dspredf) dir "E:RPM"DDTS: "shm"
MESSAGE: BC_HLTH_UPDATE
SEVERITY: InformationFORMAT: "AppId 0x%x, tId 0x%x, tName %s , psl %d, bay %d, callerPc 0x%x, bcF %d, Bmap 0x%x"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "Info on caller to a SHM backcard health update API"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "config-upload"
MESSAGE: CUTW_EPID
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x)Creation of CUTW EPID \"%s\" failed rc = 0x%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "Failed to create epid(end point communication) for cutw."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 If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTW_TIMER_CREATE
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x) Creation of timer failed rc= 0x%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "Timer Creation 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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTW_ATTHDLR
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x)Attaching of handler \"%s\" failed Epid = 0x%08X rc= 0x%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "Attaching of handler to a cutw epid has failed. The epid name, number and error code are listed."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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTW_TMR_SCHD
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x) failed to schedule timer in \"%s\" timeout value = %d, timer type = %d, rc= 0x0%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "failed to schedule timeout"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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTW_TMR_CNCL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)failed to cancel timer in \"%s\" timer type = %d, rc= 0x0%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "failed to canecl timer"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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTW_IPC_FREE_ERR
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x) IPC Message Free Failed : rc = 0x%08X."FLAG: No FlagLIMIT: One TickEXPLANATION: "Error in Freeing IPC message"RECOMMENDED ACTION: If this event shows up excessively (about 5 or more times) in the event log, please log a bug and contact TAC immediately. This is a potential memory leak.REQUIRED_INFO: If CLI available, capture the following command output before contacting TAC:1) dspversion2) dspdate3) dspmempart 2 14) dsplog -mod CUTS5) dsplog -mod CUTWRKRMESSAGE: IPCFAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x) IPC SEND FAILED TO \"%s\" from \"%s\" request:%d"FLAG: No FlagLIMIT: One TickEXPLANATION: "IPC send 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: If CLI available, capture the following command output before contacting TAC:1) dspversion2) dspdate3) dspmempart 2 14) dsplog -mod CUTS5) dsplog -mod CUTWRKRMESSAGE: IPC_ALLC_FAILED
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x) failed to allocate ipc buffer in \"%s\"."FLAG: No FlagLIMIT: One TickEXPLANATION: "failed to allocate ipc buffer. This will cause CUTS not able to communicate with this 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: If CLI available, capture the following command output before contacting TAC:1) dspversion2) dspdate3) dspmempart 2 14) dsplog -mod CUTS5) dsplog -mod CUTWRKRMESSAGE: CUTW_INVALID_RQ
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x) Invalid request received by cutw from system epid: req = %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Invalid request received"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTW_EPID_RESOLVE
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x) CUTW %s could NOT resolve CUTS epid"FLAG: No FlagLIMIT: One TickEXPLANATION: "Not able to resolve the scheduler task's epid"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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTW_WRKR_UPDAT
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x) failed to update the worker task of index (%d) to state %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "CUTW unable to update worker task state"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTW_INIT_PTR
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x) CUTW Task init failed due to a NULL taskControlBlockPtr in %s, tid = 0x%0X"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "CUTW init failed due to a null task controlblock ptr"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: If CLI available, please capture the following command output before contact TAC:1) dspversion2) dspdate3) dsplog -mod CUTS4) dsplog -mod CUTWRKR5) dsplogMESSAGE: CUTW_FC_FAILED
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x) cutw failed to process file creation request for file 0x%08X."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to validate file creation request"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BAD_FILEINDX
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x) Invalid File index found in \"%s\" file Index = %d."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw found an invalid file index "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CUTWFILENAME
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)filename created for the request is \"%s\" file Index = %d."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw created the name for the file creation request "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: W_RATEVENTPENDING
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x) RAT event %d pending found while creating file Index = %d."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw had to abort while creating a file due to rat events "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: NULL_FILEP
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)(cutw) NULL FILEPTR PASSED IN to %s routine"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw found an invalid file ptr "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TASK_STATUS_TRANS
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)(cutw) Task status transition from \"%s\" to \"%s\"."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Task is transitioning from one state to another"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEMTAKE_FAIL
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)(cutw) Can't take semaphore for \"%s\" in function \"%s\"."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw was not abe to take a semaphore"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEMGIVE_FAIL
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)(cutw) Can't release semaphore for \"%s\" in function \"%s\"."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw was not abe to release a semaphore"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: NULL_PTR
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)(cutw) NULL pointer PASSED IN to \"%s\" routine"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw found a null ptr "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: MEM_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)failed to allocate mem for %s for file index %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to allocate buffer. This Config Upload file creation request will not be successful. "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: MEMDEALL_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)failed to deallocate mem for %s for file index %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to deallocate buffer. This could lead to memory leak "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RTOID_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)failed to write ROOT OID for file index %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to write root oid which cause this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TBLOID_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)failed to write ROOT OID for file index %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to write table oid which cause this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CNFOID_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)failed to write item OID %d,col %d, for file index %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to write item oid which cause this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CNFVRBND_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)failed to write CNFVRBND table %d,col %d, for file index %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to write cnfg varbind which causes this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: FINDOBJ_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)find_object failed for oidTbl->oidListInx=%u for file %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw cannot find the current OID which causes this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: GTNXT_FAIL
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)(cutw)Empty Table found, continuing.. for file %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw found an empty table "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: WRITE_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)failed to write %s for file %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to write data to file which causes this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: GET_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)File %d Serial# %d oid %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to do a get operation which causes this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: GETNEXT_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x) Serial# %d type %d oid %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to do a get-next operation which causes this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: GETSCLR_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw) Get failed for object table %d,col %d for file %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw write failed "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: IOCTL_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw)call to %s failed while creating file %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw ioctl call failed "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CR_RESULT
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)(cutw)FILE CREATION RESULTED IN %s for file %d : File size: %ld : Checksum: %x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw file creation result "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: FILE_ERR
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw) %s for file %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw file creation result "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: WRITE_BYTESFAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutw) Write Fail for File %d: requested bytes %d bytes written %d."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw failed to write requested number of data to file which causes this Config Upload file creation aborted "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: MAX_ROWS_EXCEEDED
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x)(cutw) Write Fail for File %d: Too many rows: limit is %d, currently %d. oidTblInx=%d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutw aborted the file creation because number of rows allowed for this file exceeded the defined limit"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: INVALID_PARAM
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Invalid parameter passed: 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Invalid parameter was received by the function"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TXID_GET_FAILED
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Config upload failed to receive a valid TxId from the card"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Config upload failed to receive a valid TxId from the card"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TIME_GET_FAILED
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to get current time of day"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to get current time of day"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: OPEN_FAILED
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to open file %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to open a file"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: FNAME_PARSE_ERROR
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to parse filename %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to parse a filename"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BITMAP_FAILURE
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to get connection bitmap"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to get the connection bitmap"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: NULL_ERRHDLR
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)No error handler found, fileType=%d, i=%d, j=%d, k=%d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to read enoughd data from alarm file"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: FILE_READFAIL
EVERITY WarningFORMAT: "(Line %d:errno 0x%x): (cutv) cannot open file (fd:%d, name:%s) with read permission in function %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutv failed open file with read permission"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: REMOVE_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutv) remove failed for %s infunction %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "cutv cannot remove the file. remove failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: VLDN_THRESH_EXCEED
SEVERITY: InformationFORMAT: "(Line %d:errno 0x%x)(cutv) failed to open file with read permission too many times in %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "validation counter exceeded threshold"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RMT_FILE_IOCTL_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)(cutv) remote file ioctl fail in %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "remote file ioctl failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: LATEST_STATIC_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to find the latest static conn file"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to find the latest static conn file"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: INVALID_REQ
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Invalid request given to the engine: %d, filetype =%d\n"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Invalid request given to the engine"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: REQ_PROC_INVALID
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Invalid request processing entry in the request matrix, reqtype=%d, filetype =%d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Invalid request processing entry in the request matrix"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: INVALID_PROC_PARTS
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Invalid processing parts reqtype=%d, filetype =%d, totalProcessingParts=%d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Invalid request processing entry in the request matrix"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: INVALID_SLOT
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Invalid slot "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to get slot# from CTC"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEEK_UPDATE_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to seek into file for updating length"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to seek into file for updating length"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: REPLICATE_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to replicate the file %s to standby PXM"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Asynchronous file replication API failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: INVALID_REQ_TXID
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Config upload received a requested TxId larger than the card TxId"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Config upload received a request to create incremental file with TxId larger than the one on the card"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: TXID_AUDIT_FAILED
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Config upload requested audit of card TxId and the audit failed"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Config upload received a request to create incremental file with TxId larger than the one on the card. It requested audit of card TxId and it could not be fixed."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: CHKSUM_FAILURE
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Checksum failed for file %s: compChecksum=0x%x, readChecksum=0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "One byte checksum in the file did not match with the calculated checksm"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: MEM_ALLOC_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to allocate %d bytes in memory"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Memory allocation failure"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: ALARM_BUFF_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to get latest alarm file data "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to get latest alarm file data from cPro/conPro applications"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: STBY_REMOVE_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to remove %s from stdby"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to get latest alarm file data from cPro/conPro applications"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO No required infoMESSAGE: STATIC_DEL_FAIL
SEVERITY: ErrorFORMAT: "(Line %d:errno 0x%x)Static file deletion resulted in %s for slot %d on controller card %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to remove static connection files from a controller card. There might be disk issues (refer errno)"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: DIR_CHECK_FAIL
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Failed to check directory %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "There was an error encountered while checking for the directory specified. This could be because the dir name was invalid or because the init dirs failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: ADDINT_FAILURE
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x)Overflow in the working pointer on call to AddInt. wrkPtr = 0x%x, tmpPtr = 0x%x, TxId = %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "There was an error on call to AddInt api that encodes the TxId in ASN.1 format. It overwrote extra amount of memory"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO No required infoMESSAGE: SANITY_FAILURE
SEVERITY: WarningFORMAT: "(Line %d:errno 0x%x) Sanity check failed: %s :0x%x, 0x%x "FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "There was an error on call to AddInt api that encodes the TxId in ASN.1 format. It overwrote extra amount of memory"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "diskdb"
MESSAGE: DBCLNT_INFO
SEVERITY: InformationFORMAT: "%s %s <0x%x> %s"FLAG: No FlagLIMIT: One TickEXPLANATION: "The INFO string should be self-explained."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "shm"
MESSAGE: NFATAL_MAJ_ERPT3
SEVERITY: InformationFORMAT: "%s: AppId 0x%x, tId 0x%x, tName %s , Ref. pslot %d, callerPc 0x%x, evtNum 0x%x"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "Info on caller to a SHM fatal error resource report API"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: FRUMISMATCH_RPT
SEVERITY: InformationFORMAT: "AppId 0x%x,tId 0x%x,tName %s,pslot %d,bay# %d callPc 0x%x,BcCnfState %d,Mismatch[Aps 0x%x,NonAps 0x%x)"FLAG: Stack Trace|Write BramLIMIT: No ThrottlingEXPLANATION: "Info on caller to a BackCard FRU Mismatch State Change report API"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BC_HLTH_UPDATE
SEVERITY: InformationFORMAT: "AppId 0x%x, tId 0x%x, tName %s , psl %d, bay %d, callerPc 0x%x, bcF %d, Bmap 0x%x"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "Info on caller to a SHM backcard health update API"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: IP_NOT_CONFIGURED
SEVERITY: InformationFORMAT: "%s: AppId 0x%x, tId 0x%x, tName %s, callerPc 0x%x, %s"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "SHM query for IP address returned error IP not configured "RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: GEN_ERROR
SEVERITY: InformationFORMAT: "Line %d: %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Reports a SHM general error, the event contains more details"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.MESSAGE: EPID_CREATE_ERR
SEVERITY: ErrorFORMAT: "SHM ERR: Epid Create Failed in %s, Errno = 0x%x"FLAG: No FlagLIMIT: One TickEXPLANATION: "ssiIpcComEpCreate failed, check the Errno."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 Technical support representative.MESSAGE: SFM_SEND_ERR
SEVERITY: ErrorFORMAT: "Sfm Send failed, AppId 0x%x, tId 0x%x, tName %s , Ref. pslot %d, callerPc 0x%x, Evt Num: 0x%x, Msg Type: 0x%x, Reason: %s"FLAG: Write BramLIMIT: One TickEXPLANATION: "This provides the information when a card fails to come up due to IPC version mismatch."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 Technical support representative.MESSAGE: INTERCD_APS_RPT
SEVERITY: InformationFORMAT: "%s: AppId 0x%x, tId 0x%x, tName %s , Ref. pslot %d, callerPc 0x%x, evtNum 0x%x"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "Info on caller to a SH inter-card aps resource report API"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS:"ssi"
MESSAGE: HANGTASK_MSEC
SEVERITY: Minor AlertFORMAT: "Task %p[%s] has been %s at %p for %d milliseconds."LIMIT: One TickEXPLANATION: "The system has a critical task that is hung on the specified object for the specified time. This event is same as HANGTASK except display in milliseconds format"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 infoMESSAGE: ATADRVERR
SEVERITY: ErrorFORMAT: "ATA driver error. %s (%s), retry: %d.cyl: 0x%x, head: %d, sec: %d, nSec: %d"LIMIT: One MinuteEXPLANATION: "The ATA driver detected a HDD status error. This error event contains the device registers of hardware devices between the CPU and the HDD. Please contact the TAC engineers to analysis the captured data and recommend a recover action, if required. Use dsperr (not dsperrs) to display all data capture in this error event log."RECOMMENDED ACTION: "Capture the output of dsperr command on the PXM slot in which the problem occurred."REQUIRED_INFO: No required infoMESSAGE: ATAWAITERR
SEVERITY: ErrorFORMAT: "ATA driver error (%s). mask: 0x%x, req: 0x%x"LIMIT: One MinuteEXPLANATION: "The ATA driver detected a HDD status error. This error event contains the device registers of hardware devices between the CPU and the HDD. Please contact the TAC engineers to analysis the captured data and recommend a recover action, if required. Use dsperr (not dsperrs) to display all data capture in this error event log."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 infoMESSAGE: ATADRVINFO
SEVERITY: InformationFORMAT: "ATA driver info. %s (%s), retry: %d.cyl: 0x%x, head: % d, sec: %d, nSec: %d"LIMIT: One MinuteEXPLANATION: "The ATA driver detected a HDD IO operation failure This error event contains the device registers of hardware devices between the CPU and the HDD. This event is for information only."RECOMMENDED ACTION: No action requiredREQUIRED_INFO: No required infoMESSAGE: HNGNOSTKTRC
SEVERITY: Minor AlertFORMAT: "Task %p[%s] has been %s at %p for %d minutes."FLAG: Write BramLIMIT: One TickEXPLANATION: "The system has a task that is hung on the specified object for the specified time. This event is same as HANGTASK except that trace is not dumped because the semaphore that is necessary to dump the trace is not available."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 infoDDTS: "shm"
MESSAGE: FUNC_FAILED
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagLIMIT: One TickEXPLANATION: "tRed function call failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO No required infoMESSAGE: SRM_UNAVAIL
SEVERITY: WarningFORMAT: "%s : Bay %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "SRM for the particular bay is not available"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: MAKE_HSB_ACTIVE_FAILED
SEVERITY: WarningFORMAT: "%s, Slot %d, Redundant slot %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Error in making HSB go Active"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: SEC_CD_INFO
SEVERITY: InformationFORMAT: "%s, red type=%d,state= %d, slot %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "Setting the Secondary card state"RECOMMENDED ACTION: No action requiredREQUIRED_INFO: No required infoMESSAGE: AC_TIME_OUT_ERR
SEVERITY: InformationFORMAT: "State Time out %s, slot %d"FLAG: Stack TraceLIMIT: One SecondEXPLANATION: "Auto Card time out error."RECOMMENDED ACTION: No action requiredREQUIRED_INFO: No required infoMESSAGE: AC_DWNLBRAMERR
SEVERITY: InformationFORMAT: "ACRED: Download BRAM Failed %s. From %d to %d"FLAG: Stack TraceLIMIT: One SecondEXPLANATION: "BRAM download error."RECOMMENDED ACTION: No action requiredREQUIRED_INFO: No required infoMESSAGE: AC_UPLDBRAMERR
SEVERITY: InformationFORMAT: "Upload BRAM Failed %s , Pslot %d, Lslot %d"FLAG: Stack TraceLIMIT: One SecondEXPLANATION: "BRAM upload error."RECOMMENDED ACTION: No action requiredREQUIRED_INFO: No required infoMESSAGE: DUPLICATE_CONNID_EXISTS
SEVERITY: ErrorFORMAT: "rec: %d; conn (%d.%d.%d) already exists in rec# %d;"FLAG: No FlagLIMIT: One TickEXPLANATION: "duplicate conn. entry found in a different record"RECOMMENDED ACTION: "This event is logged when the same connection id exists on two different connection records"REQUIRED_INFO: "From both active and standby PXM cards,1) zip the event/error logs2) save the config (saveallconfig)3) ftp over the config and log zip files."DDTS: "diskdb"
MESSAGE: RESV_NO_DB
SEVERITY: ErrorFORMAT: "Slot %d: %s"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: " The slot is pseudo-resv and reserved from th SHM perspective but its DB2 directory does no have any DBs for the specified slot"RECOMMENDED ACTION: "Call TAC"REQUIRED_INFO: "Save event logs, error logs and ll from D:/DB2"MESSAGE: NO_PSEU_NO_RESV
SEVERITY: Major AlertFORMAT: "Slot %d: %s"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: " The slot is not pseduo reserved, not reserved form SHM perspective but its DB is existed i DB2 directory"RECOMMENDED ACTION: "Call TAC"REQUIRED_INFO: "Save event logs, error logs and ll from D:/DB2"MESSAGE:DETECT_UNDESIRE
SEVERITY: WarningFORMAT: "Slot %d info: %s"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "The slot is detected with the specified undesire info."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: PSEUDO_ONLY
SEVERITY: InformationFORMAT: "Slot %d info: %s"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "The slot is detected with pseudo reserved only"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: DBSVR_TRAPWARNING
SEVERITY: WarningFORMAT: "%s:%s- %s "FLAG: No FlagLIMIT: One TickEXPLANATION: "DB Server fails to generate Trap."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "diskdb"
MESSAGE: DBSYNC_INFO
SEVERITY: InformationFORMAT: "%s:%s %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "DB Sync detected some info condition"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoDDTS: "ssi"
MESSAGE: MBLKBUFFREEFAIL
SEVERITY: ErrorFORMAT: "Failed to free data buffer %x, errno %x, callerPc 0x%x"FLAG: No FlagLIMIT: One TickEXPLANATION: "Failed to free data buffer"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 Technical support representative.MESSAGE: MBLKFREEFAIL
SEVERITY: ErrorFORMAT: "Failed to free mblk %x, errno %x, callerPC:0x%x"FLAG: No FlagLIMIT: One TickEXPLANATION: "Failed to free mblk"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 Technical support representative.DDTS: "snmp-ma"
MESSAGE: EPIDWARN
SEVERITY: WarningFORMAT: "Parm %s value '0x%x' is invalid to %s."FLAG: No FlagLIMIT: Ten SecondsEXPLANATION: "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: "On PXM:1. dspcds2. dsplog3. dsperr4. dsprev"MESSAGE: EPIDERROR
SEVERITY: ErrorFORMAT: "Parm %s value '0x%x' is invalid to %s."FLAG: Stack Trace | Write BramLIMIT: One HourEXPLANATION: "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: "On PXM:1. dspcds2. dsplog3. dsperr4. dsprev"DDTS: "ctc"
MESSAGE: RATERR030
SEVERITY: WarningFORMAT: "Ack for RAT \"%s\", task \"%s\" (%d) with unexpected status \"%s\" (0x%08X). pRat 0x%x pMblk 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "The task receive ACK from it child but it child's status is not in processing mode. This will result in child's status to set to fail."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR031
SEVERITY: WarningFORMAT: "RAT \"%s\" task offset (%d) exceeds range (%d). pRat 0x%x, pMblk 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Timeout event receive from a child outside the range of the table"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR054
SEVERITY: WarningFORMAT: "Invalid Child Id. pRat 0x%x, pMblk 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "The task received message from unknown source"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR056
SEVERITY: WarningFORMAT: "Received unexpected message from child (offset = %d). pRat 0x%x pMblk 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "We shouldn't receive a message from a task where there aren't any outstanding requests"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR057
SEVERITY: WarningFORMAT: "Invalid state!!! offset = %d, state = (\"%s\"). pRat 0x%x pMblk 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "The state of the child entry is invalid. Task failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR058
SEVERITY: WarningFORMAT: "Unexpected response received from child task. offset = %d, expected resp = \"%s\". pRat 0x%x pMblk 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Unexpected response received from child task. The response should be OK"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR059
SEVERITY: WarningFORMAT: "ssiTimeoutCancel(), Can not cancel timeout timer for offset %d, result %d, pRat 0x%x pMblk 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Can not cancel timeout timer for child task"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR060
SEVERITY: ErrorFORMAT: "ssiIpcMessageFree(), Can not free message for offset %d, result %d, pRat 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Can not free memory. This can result in potential memory leak"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, 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 Technical support representative.MESSAGE: RATERR061
SEVERITY: WarningFORMAT: "ssiTimeoutCancel(), Can not cancel overall timer, result %d, pRat 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Cancellation of timer failed"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR062
SEVERITY: WarningFORMAT: "Role change attempt to \"%s\" results in \"%s\". pRat 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Failed to transition to new state."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: RATERR063
SEVERITY: ErrorFORMAT: "at end of rat_comEpWait_msgHdlr() state (\"%s\") is invalid. pRat 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "The task is not successfully transition to new state"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, 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 Technical support representative.MESSAGE: RATERR084
SEVERITY: ErrorFORMAT: "Corrupted msg from RAT %s, task \"%s\" (%d), cookie = 0x%08X, pRat 0x%x pMblk 0x%x."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "A message was received whose magic cookie 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. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, 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 Technical support representative.DDTS: "axsm_apps"
MESSAGE: APS_ERROR
SEVERITY: NoticeFORMAT: "APS Error: line %d, %s : 0x%x"FLAG: Stack TraceLIMIT: No ThrottlingEXPLANATION: "APS Task 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: Capture the output of these CLIsOn PXM45:a) dsplog -sl <slot that experienced the error>b) dsperr -sl <slot that experienced the error>DDTS: "ssi"
MESSAGE: BELOWTHRES
SEVERITY: WarningFORMAT: "Cannot allocate %d bytes. Not enough %s prio mem exists in mempart %d. Thresh %d bytes, Free %d bytes."FLAG: Stack TraceLIMIT: One SecondEXPLANATION: "Allocation failed because number of free bytes is below threshold. Currently there is a limit on the bytes available for low and high priority allocation requests. These limits are visible using the dspmempart command for a given partition. This can be the result of a memory leak in the partition."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoMESSAGE: NOPARTITION
SEVERITY: WarningFORMAT: "Could not allocate %d bytes from partition 0x%x for %s priority data (errno 0x%x)."FLAG: Stack TraceLIMIT: One SecondEXPLANATION: "An error was returned by ssiMalloc while attempting to allocate low or high priority memory. If critical memory allocation, then memPartAlloc 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 infoMESSAGE: DOWNSTATIC
SEVERITY: WarningFORMAT: "Not enough memory in the dynamic pool for %d bytes, trying static"FLAG: Stack TraceLIMIT: One SecondEXPLANATION: "The dynamic partition does not have enough space to allocate the specified number of bytes. The software will try to allocate the space from the static partition."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoMESSAGE: DOWNVXWORKS
SEVERITY: WarningFORMAT: "Not enough memory in the static pool for %d bytes, trying VxWorks' heap"FLAG: Stack TraceLIMIT: One SecondEXPLANATION: "The static partition does not have enough space to allocate the specified number of bytes. The software will try to allocate the space from the VxWorks heap."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoMESSAGE: ERRBUFFCORR
SEVERITY: ErrorFORMAT: "Error buffer corruption detected and re-init. %s. List 0x%x, node 0x%x, next 0x%x, count %d"FLAG: Write BramLIMIT: One TickEXPLANATION: "SSI detected Error and Trace buffers corruption. The trace and error buffers are re-initialized during card boot-up. Some trace and/or error events may be lost."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: "Event, error logs, core dump, and the output of shell command 'logConsoleShow'. Events logs must include all the entries that had occurred 15 minutes before the time of this event."MESSAGE: HANGTHRESH
SEVERITY: ErrorFORMAT: "hangThresh %d or starvationThresh %d is invalid, caller PC 0X%x."FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "task starvation or hang threshold value is out of range. threshold is used by task monitor to determine the task starvation or hang situation"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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: 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 Technical support representative.DDTS: "shm"
MESSAGE: SCM_PARMS_CHG
SEVERITY: InformationFORMAT: "Change SCM Poll Parms: MaxPollRetry, MaxMissPoll, MonFromStby: From %d, %d, %d To: %d, %d, %d."FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "User is changing the SCM poll parms"RECOMMENDED ACTION: No action requiredREQUIRED_INFO: No required infoMESSAGE: MCAST_VER_CHG1
SEVERITY: WarningFORMAT: "mcastSenderVersion invalid, changing it from %d to %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The global variable that has the multicast version is accidently changed to invalid. This event indicates that it has been changed back to its value."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoMESSAGE: MCAST_VER_CHG2
SEVERITY: WarningFORMAT: "global var (%d), node db (%d) copies of mcastSenderVersion are invalid, changing to %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The global variables that have the multicast version are accidently changed to invalid. This event indicates that they have been changed back to normal expected value."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED_INFO: No required infoMESSAGE: MASTERSHIP_REL
SEVERITY: InformationFORMAT: "Slot %d is releasing its mastership by deasserting FWREADY bit"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "The Mastership is being released to the other PXM."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BC_INFO_FIXED
SEVERITY: InformationFORMAT: "pslot %d, bay %d, hasBcF %d, hasBmap %d, bcFailed %d, bmap 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "This event will be logged when bcFailed is TRUE but bmap is either missing or contains no failure bit in the BC insert message. The bmap will be changed internally to indicate unknown BC failure."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BC_BMAP_INV
SEVERITY: InformationFORMAT: "pslot %d, bay %d, bcFailed %d, bmap 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "This event will be logged when unknown bits are detected in the BC health bitmap in the BC insert event message."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BC_INFO_IGNORED
SEVERITY: InformationFORMAT: "pslot %d, bay %d, hasBcF %d, hasBmap %d, bcFailed %d, bmap 0x%x"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "This event will be logged when either (1) EXTPOLL_BC_FAILED_OID is missing or (2) BC health info inconsistency is detected the BC insert event message."RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: BC_HLTH_CHNGED
SEVERITY: InformationFORMAT: "%s: pslot %d, bay %d, oldBcF %d, newBcF %d, oldBmap 0x%x, newBmap 0x%x"FLAG: Write BramLIMIT: No ThrottlingEXPLANATION: "BC Health Info update"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: MC_VER_CHG
SEVERITY: WarningFORMAT: "Multicast receiver in pslot %d can only support upto version %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "The multicast receiver at the indicated slot cannot understand the sender's version. Sender will adjust to lower version"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: API_CALL_ERR
SEVERITY: ErrorFORMAT: "API %s, called by SHM returned Error (0x%x)"FLAG: No FlagLIMIT: One TickEXPLANATION: "SHM_ERR: An API called by SHM 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: 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 Technical support representative.MESSAGE: XBAR_NOT_UP
SEVERITY: InformationFORMAT: "%s reported against xbar slot: %d, xbarPlane: %d, errPSlot: %d, errType: %d, errSeverity:%d, %s"FLAG: No FlagLIMIT: One TickEXPLANATION: "There was an error reported on xbar slot which is either not present or the xbar is not enabled yet, not shuting down the link"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: HV_PORT_INVALID
SEVERITY: InformationFORMAT: "Humvee Error reported against invalid/unused port: %d for Slot: %d, errType: %d, errSeverity: %d"FLAG: No FlagLIMIT: One TickEXPLANATION: "There was an error reported on a invalid humvee port, so not processing the error"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: MASTERSHIP_OK
SEVERITY: InformationFORMAT: "Mastership bits ok IM IR HM HR HCR: From: %s %s %s %s %s To: %s %s %s %s %s, Log Count: %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "The Mastership bits went to ok state from an invalid state"RECOMMENDED ACTION: No Recommended ActionREQUIRED_INFO: No required infoMESSAGE: HW_LOG_TRAP_ERR
SEVERITY: ErrorFORMAT: "Trap Send Failed: %s, Error Code: %d"FLAG: No FlagLIMIT: No ThrottlingEXPLANATION: "Trap send 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: 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 Technical support representative.