MGX and SES Error Messages, Release 4
MGX and SES Error Messages, Release 4 (part B3)
-
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
DAL-2-DAL_INIT_ERR_ST
SEVERITY: Major AlertFORMAT: "DAL Init Err line %d errno=0x%X,0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the DAL module driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-4-DAL_ERR
SEVERITY: ErrorFORMAT: "DAL Err line %d errno=0x%X,0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-4-DAL_ERR_STR
SEVERITY: ErrorFORMAT: "DAL Err line %d errno=0x%X,0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd "DAL-5-DAL_WARNING
SEVERITY: WarningFORMAT: "DAL Warning line %d errno=0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an warning detected by the DAL module."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection"DAL-5-DAL_WARNING_STR
SEVERITY: WarningFORMAT: "DAL Warning line %d errno=0x%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an warning detected by the DAL module."RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspchancnt on the problem connection"DAL-7-DAL_INFO
SEVERITY: InformationFORMAT: "DAL Info line %d errno=0x%X,0x%X,0x%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DAL Informational Event."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "pxm-diag"
PXMD-4-ERR
SEVERITY: ErrorFORMAT: "Line %d , Diagnostic error : %s, 0x%x, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A diagnostic error occurred"RECOMMENDED ACTION: "Replace the card that reported this error. Call your Cisco technical support representative."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 "pxm1e"
EM-4-EM_ERROR
SEVERITY: ErrorFORMAT: "EM ERROR %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates an internal error detected by the EM application. It needs to be analyzed by TAC and possibly by the development team. In normal operation, such an error should never get reported."RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative "REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot that experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified above.On Service Module1. dspcd2. dsplns3. dspports4. dspparts5. dspapslns (for SONET cards) "EM-7-EM_EVENT
SEVERITY: InformationFORMAT: "EM Event %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "EM Informational Event"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoEM-2-NOVRAM_READ_ERR
SEVERITY: Major AlertFORMAT: "NOVRAM Read Error %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This error indicates a failure reading the NOVRAM. This failure can be for one of the following NOVRAMs1. Front Card NOVRAM2. Daughter Card NOVRAM3. Back Card NOVRAM"RECOMMENDED ACTION: "If the error is indicated for Front Card or Daughter Card NOVRAM, please replace the Front Card. Replace the Back Card if error is indicated for Back Card NOVRAM. In most cases, NOVRAM read failures are a direct result of a hardware failure. However, if you suspect that the error was caused due a certain operator action or a system event, please capture the following information and contact your Cisco support representative "REQUIRED INFO: "Please capture following information on PXM451. dspcds2. dspcd <slot>3. dsplogOn Service Module, please capture the following information1. dspcd2. dsplns "EM-2-LINE_HARDWARE_E
SEVERITY: Major AlertFORMAT: "Line Hardware Error on line %d.%d\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This error indicates a hardware failure for the specified line. The failure is typicaly due to a front-card hardware problem."RECOMMENDED ACTION: "Please replace the Front Card if the problem persists across reboots. Note that if this error is detected on a standby card, it will automaticaly reboot. If the error is detected on an active card, the card will continue to function. However, the dspcds command on PXM45 will show that the card state is Active-F. Contact your Cisco support representative if you suspect that a certain operator action or a system event caused this error."REQUIRED INFO: "Please capture the information with following commands on the active service module1. dspcd2. dsplns3. dspalmsPlease capture the system log with dsplog <slot> command on PXM45."EM-2-DAUGHTER_CARD_M
SEVERITY: Major AlertFORMAT: "Unknown/Missing Daughter Card on bay %d\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This error indicates a failure in recognizing the Daughter Card in the specified bay. This can happen due to one of the followng reasons1. Daughter Card NOVRAM is not readable2. Daughter Card Type specified by NOVRAM is not supported3. A Daughter Card is not installed.This error is detecting during the booting phase. "RECOMMENDED ACTION: "Please replace the Front Card as it is not usable. Note that this error will take the card in Active-F state. If the error is detected on a standby card, it will cause the card to reset. Please capture following information and contact your Cisco support representative if you suspect that a certain operator action or a system event caused this error "REQUIRED INFO: "Please capture following information on PXM451. dspcds2. dspcd <slot>3. dsplogOn Service Module, please capture the following information1. dspcd2. dsplns "EM-2-PRTSTAT
SEVERITY: Major AlertFORMAT: "Port State Port%d Oper State%s \n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Change in port operation state. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_ERROR to make it more visible for customer."RECOMMENDED ACTION: "Port operation state changes according to line state. Check line for alarms and take appropriate corrective actions on physical line."REQUIRED INFO: No Required InfoDDTS "ccma"
OAM-7-LOG
SEVERITY: InformationFORMAT: "OAM event %s %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Oam Informational Event"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoOAM-4-ERROR
SEVERITY: ErrorFORMAT: "OAM error %s %s\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Indicates a software error detected by the oam task. Need to contact TAC for the problem."RECOMMENDED ACTION: "Call your Cisco technical support representative and pass the captured info to the representative."REQUIRED INFO: "Capture the following info from the switch On pxm1e 1>dspcd <slot number of the active card> 2>dspver 3>dspcds 4>dsppnports 5>dsplog -sl <slot number of active pxm1e card> 6>dsperr -sl <slot number of active pxm1e card> 7>dsplns 8>dspports 9>dspparts 10>dspapslns (for SONET cards)"DDTS "pxm-diag"
PXM4-4-ERR
SEVERITY: ErrorFORMAT: "Diagnostic error : Error %s, %d, 0x%x, 0x%x, 0x%x\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A diagnostic error occurred"RECOMMENDED ACTION: "Replace the card that reported this error. Call your Cisco technical support representative."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 "ccma"
QE48-5-QE48ERR
SEVERITY: WarningFORMAT: "QE48 Err Status%s reg 0x%x,%s reg 0x%x,%s reg 0x%x,%s reg 0x%x,%s reg 0x%x"FLAG: Write to BramTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoQE48-5-QE48ERR2
SEVERITY: WarningFORMAT: "QE48 Err Status%s reg 0x%x, %s reg 0x%x,%s reg 0x%x,%s reg 0x%x"FLAG: Write to BramTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "ccma"
QE48-5-QE48SARERR
SEVERITY: WarningFORMAT: "QE48SAR Error %s() line %d %X,%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "drivers"
QE-4-FAIL2REFRESH
SEVERITY: ErrorFORMAT: "QE Initialization Error qeInitConfigReg; qe_no = %d Refresh failed"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The specified QE is unable to initialize durring the refresh cycle."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoQE-4-EXPMANTISAFAIL
SEVERITY: ErrorFORMAT: "QE Initialization Error qeSetAcpCellCntRam; qe_no = %d GetExpMantisa failed"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The specified QE is unable to convert Cell Loss Threshold into Exp format."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoQE-5-UNKNOWNINT
SEVERITY: WarningFORMAT: "QE Unknown Interrupt Error EQ No %d, status1 = %d, status2 = %d, status3 = %d\n"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The specified QE got unknown interrupt signal from the system."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoQE-5-ERRINTERRUPT
SEVERITY: WarningFORMAT: "QE Unknown Interrupt Error QE No %d, status1 = %d, status2 = %d, status3 = %d\n"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The specified QE got error interrupt signal from the system."RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.REQUIRED INFO: No Required InfoQE-4-QE_ERR
SEVERITY: ErrorFORMAT: "QE Err %s() line %d %X,%X,%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The followings could be the error that is log by the node Adding Ingress/Egress to Hmm device list, Not valid device ID Hmm init DB error, Invalid pointer(s)"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoQE-5-QE_ERR_STR
SEVERITY: WarningFORMAT: "QE Err %s() line %d %X,%X,%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Device that are not supported by QE"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "drivers"
QE12-4-QESAR_ERR
SEVERITY: ErrorFORMAT: "QE1210 SAR Error line %d %X,%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An Error condition has been detected by QE SAR module. In normal operation, such an error should never get reported."RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. do QE register dump"QE12-5-QESAR_WARN
SEVERITY: WarningFORMAT: "QE1210 SAR Warning line %d %X,%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A Warning condition has been detected by QE SAR module"RECOMMENDED ACTION: "If there is traffic loss, please capture the following information and call your Cisco Technical Support Representatives"REQUIRED INFO: " On PXM451. dspcd <slot that experienced the error>2. dspred3. dsplog -sl <slot the experienced the error>4. dsplog -sl <other slot in the pair if redundancy is configured>5. dsperr for slots specified aboveOn Service Module1. dspcd2. do QE register dump"QE12-7-QESAR_INFO
SEVERITY: InformationFORMAT: "QE1210 SAR Info line %d %X,%X"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A Warning condition has been detected by QE SAR module"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "shm"
RED-7-MSGQSEND
SEVERITY: InformationFORMAT: "ACRED Could not send MSG to SM "FLAG: No FlagTHROTTLING: One TickEXPLANATION: "AC_SEND_MSG_FAILED_ERR"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRED-7-GENERAL
SEVERITY: InformationFORMAT: "ACRED General ERROR"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "AC_GEN_ERR"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRED-7-INFORM
SEVERITY: InformationFORMAT: "ACRED Informational"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "AC_INFO_ERR"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRED-7-MEMCORRT
SEVERITY: InformationFORMAT: "ACRED Memory corruption in system"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "AC_MEM_ERR"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRED-7-TIMEOUT
SEVERITY: InformationFORMAT: "ACRED State Time out"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "AC_TIME_OUT_ERR"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRED-7-WRONGMSG
SEVERITY: InformationFORMAT: "ACRED Wrong Message Received"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "AC_WRONG_MSG_ERR"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRED-7-DNLDERR
SEVERITY: InformationFORMAT: "ACRED Download BRAM Failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "AC_DWNL_BRAM_ERR"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRED-7-UPLDERR
SEVERITY: InformationFORMAT: "ACRED Upload BRAM Failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "AC_UPLD_BRAM_ERR"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoDDTS "red"
REDM-7-CR_ERR
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "pnRedman is not able update standby controller on a given connection, due to either memory low or invalid request, etc."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-P2P_ADD_FAIL
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-P2P_DEL_FAIL
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-P2MP_ADD_FAIL
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-P2MP_DROP_FAIL
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-INVALID
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "pnRedman receives some invalid value, such as message, event"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-NULL_PTR
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "a data point is NULL"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-MALLOC_ERR
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "fail to allocate memory, ipc, etc."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanInitErr
SEVERITY: InformationFORMAT: "Init Failed at %s %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanStdbySnd
SEVERITY: InformationFORMAT: "Send to standby error for %s "FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanIovErr
SEVERITY: InformationFORMAT: "IOV error for %s "FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanIpcSndEr
SEVERITY: InformationFORMAT: "Error in Ipc Send to Redman itsef "FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanMallocEr
SEVERITY: InformationFORMAT: "Memory Allocation Failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanIpcMallo
SEVERITY: InformationFORMAT: "Memory Allocation Failed for Ipc for same task"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanInValidS
SEVERITY: InformationFORMAT: "Redman is in Invalid state"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanInValidE
SEVERITY: InformationFORMAT: "Invalid Event to Redman From PROOT"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanInfo
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-pRedmanNotice
SEVERITY: NoticeFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanPrintDVa
SEVERITY: InformationFORMAT: "%s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanPrintXVa
SEVERITY: InformationFORMAT: "%s %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanError
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-prErrStk_1s1d
SEVERITY: InformationFORMAT: "%s %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-prErrStk_1s2d
SEVERITY: InformationFORMAT: "%s %d, %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-prErrStk_1s3d
SEVERITY: InformationFORMAT: "%s %d, %d, %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-ErrorStk_1s4d
SEVERITY: InformationFORMAT: "%s %d, %d, %d, %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-prErr_1s1d
SEVERITY: InformationFORMAT: "%s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-prErr_1s2d
SEVERITY: InformationFORMAT: "%s %d, %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-prErr_1s3d
SEVERITY: InformationFORMAT: "%s %d, %d, %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prErr_1s4d
SEVERITY: InformationFORMAT: "%s %d, %d, %d, %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanInfo1
SEVERITY: InformationFORMAT: "%s, %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanRootMsg
SEVERITY: InformationFORMAT: "Message Receved from root. Redman State%s, Go Event%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanTblReadE
SEVERITY: InformationFORMAT: "Table Read Error for %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: "capture dsplog -task pnRedman, dsplog -mod REDM"REDM-7-pRedmanSwCnfErr
SEVERITY: InformationFORMAT: "SwitchCnf Error. Space Not available."FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanInvalidR
SEVERITY: InformationFORMAT: "Invalid RecordNumber Received for %s."FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanMaxLimit
SEVERITY: InformationFORMAT: "Maximum Limit reached for %s."FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanMap
SEVERITY: InformationFORMAT: "For record num%d, Slot%d, subSlot%d, Port%d, subPort%d "FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanMapErr
SEVERITY: InformationFORMAT: "No mapping available for recNo%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanDiskRetr
SEVERITY: InformationFORMAT: "DiskRetry Array is full and there are 50 entries . So this entry will not be stored in disk."FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanStdByRet
SEVERITY: InformationFORMAT: "StdByRetry Array is full and there are 50 entries. So this entry will not be sent to stdby."FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanRecNo
SEVERITY: InformationFORMAT: "%s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanMaxRec
SEVERITY: InformationFORMAT: "Table Name%s, MaxNo%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanitfDsp
SEVERITY: InformationFORMAT: "%s, %d.%d.%d.%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanIfCbErr
SEVERITY: InformationFORMAT: "%s, ifCb pointer to null for given interface (ifId %d.%d.%d.%d)."FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanItfMapEr
SEVERITY: InformationFORMAT: "%s, %d.%d.%d.%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanDiskErr
SEVERITY: InformationFORMAT: "Error in Writing to Disk For %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "The provisioning command will fail because updating disk is failed"RECOMMENDED ACTION: "capture log using dsplog -mod REDM, dsplog -task pnRedman"REQUIRED INFO: No Required InfoREDM-7-pRedmanPepDsp
SEVERITY: InformationFORMAT: "%s, ifId %d.%d.%d.%d.%d vpi %d vci %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanPepMapEr
SEVERITY: InformationFORMAT: "%s, ifId %d.%d.%d.%d.%d vpi %d vci %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanPepMap
SEVERITY: InformationFORMAT: "For record num%d, ifId %d.%d.%d.%d.%d vpi %d vci %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_1s
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditInfo_1s
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_2s
SEVERITY: InformationFORMAT: "%s %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-prAuditInfo_2s
SEVERITY: InformationFORMAT: "%s %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_3s
SEVERITY: InformationFORMAT: "%s %s %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditInfo_3s
SEVERITY: InformationFORMAT: "%s %s %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_1s1d
SEVERITY: InformationFORMAT: "%s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditInfo_1s1
SEVERITY: InformationFORMAT: "%s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_1s2d
SEVERITY: InformationFORMAT: "%s %d, %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditInfo_1s2
SEVERITY: InformationFORMAT: "%s %d, %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_1s3d
SEVERITY: InformationFORMAT: "%s %d, %d %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditInfo_1s3
SEVERITY: InformationFORMAT: "%s %d, %d %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_2s1d
SEVERITY: InformationFORMAT: "%s %s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditInfo_2s1
SEVERITY: InformationFORMAT: "%s %s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_2s1d
SEVERITY: InformationFORMAT: "%s %s %d %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditInfo_2s1
SEVERITY: InformationFORMAT: "%s %s %d %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-prAuditErr_3s1d
SEVERITY: InformationFORMAT: "%s %s %s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-prAuditInfo_3s1
SEVERITY: InformationFORMAT: "%s %s %s %ds"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-RmMainLoopExit
SEVERITY: NoticeFORMAT: "Internal error redMainLoop exit"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-RmProotMsgError
SEVERITY: NoticeFORMAT: "IPC error %s. Failed to process proot event"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmStandbyUpdtRe
SEVERITY: InformationFORMAT: "Standby update receving error count exceeds threshold"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-CrJTimerErr
SEVERITY: InformationFORMAT: "CallRed journaling timer initialization failed%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmProotMsgProcE
SEVERITY: InformationFORMAT: "Failed to process root endpt message%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmInternalError
SEVERITY: InformationFORMAT: "Redman Internal Error %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmMissingProotS
SEVERITY: InformationFORMAT: "Redman received switchover from RAMDB, but failed to get msg from proot"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmActiveMsgProc
SEVERITY: InformationFORMAT: "Error processing message on active redman."FLAG: No FlagTHROTTLING: One SecondEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmStandbyUpdtRe
SEVERITY: InformationFORMAT: "Error receiving standby redman update"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmStandbyUpdtPr
SEVERITY: InformationFORMAT: "Error processing standby redman update"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmStandbyUpdtPr
SEVERITY: InformationFORMAT: "Error processing standby redman update"FLAG: No FlagTHROTTLING: One SecondEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmIpcEpCreateEr
SEVERITY: InformationFORMAT: "Ipc communication EP create failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmIpcEpResolveE
SEVERITY: InformationFORMAT: "Ipc communication EP resolve failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmIpcMsgAllocEr
SEVERITY: InformationFORMAT: "Ipc message allocation failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmIpcSendMsgErr
SEVERITY: InformationFORMAT: "Ipc send message failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-CrJTimerSchErr
SEVERITY: InformationFORMAT: "Timer schedule timeout failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-CrJTimerCancelE
SEVERITY: InformationFORMAT: "Timer cancel timeout failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmInvalidEvent
SEVERITY: InformationFORMAT: "Unexpected Event received. Curr State%d, Event%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmInvalidEventI
SEVERITY: InformationFORMAT: "Unexpected Event received. event ID%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmRamSyncErr
SEVERITY: InformationFORMAT: "RamSync error op%s, errno%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmIovAddErr
SEVERITY: InformationFORMAT: "Adding element to Iov failed. errno%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-RmActiveToStand
SEVERITY: NoticeFORMAT: "Redman exit from Active mainloop. Changed to standby role"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-RmStandbyToActi
SEVERITY: NoticeFORMAT: "Redman exit from Standby mainloop. Changed to Active role"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-RmRamDbReset
SEVERITY: NoticeFORMAT: "Redman receive reset from RAMDB. Reset reason%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-RmRemoteUnReg
SEVERITY: NoticeFORMAT: "Remote Unavailable from SyncRam Event. No more Update to Peer. Trying To send Msg%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-RmCardRoleChang
SEVERITY: NoticeFORMAT: "Card role change received from SyncRam while trying to send Msg%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmFuncTrace
SEVERITY: InformationFORMAT: "Function %s() entered"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-CrJDBInitErr
SEVERITY: InformationFORMAT: "CallRed journaling database initialization failed%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-CrInvalidNewSta
SEVERITY: InformationFORMAT: "Invalid new state posted to CallRed current state%d, new state%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-CrJDBRebuildErr
SEVERITY: InformationFORMAT: "CallRed Journalling database rebuild error%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-CrJDBChkPtDelRe
SEVERITY: InformationFORMAT: "Failed to add deleted record in checkpoint JDB"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-CrNewState
SEVERITY: NoticeFORMAT: "CallRed entering new state%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-6-CrCongestionOnO
SEVERITY: NoticeFORMAT: "Redman set standby journaling congestoin%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-5-CrRebuildIfCbNo
SEVERITY: WarningFORMAT: "Can not find IFCB during rebuild. IfId%ld"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-5-CrRebuildRootTr
SEVERITY: WarningFORMAT: "Can not get root tree for ifId%ld\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-5-CrRebuildSvcTre
SEVERITY: WarningFORMAT: "Can not get SVC tree for ifId%ld\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-CrRebuildCallRe
SEVERITY: InformationFORMAT: "Failed to add call journaling record during rebuild %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-print3
SEVERITY: InformationFORMAT: " %s %d/%d "FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-print4
SEVERITY: InformationFORMAT: " %s %d/%d/%d "FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-print5
SEVERITY: InformationFORMAT: " %s %d/%d/%d/%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-print1s5d
SEVERITY: InformationFORMAT: " %s %d,%d,%d,%d,%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanRevChgRe
SEVERITY: InformationFORMAT: "DiskTable Rev Change Register error. TableId%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanRevRegDo
SEVERITY: InformationFORMAT: "DiskTable Rev Change Register Done error. TableID%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-pRedmanMaxAccIn
SEVERITY: InformationFORMAT: "DiskTable Max Access Info Get error. TableID%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-RmRamSyncRevChg
SEVERITY: InformationFORMAT: "RamSync Rev Change Register error. TransID%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A software error occurred"RECOMMENDED ACTION: "capture dsplog -task pnRedman, dsplog -mod REDM"REQUIRED INFO: No Required InfoREDM-7-RmRamSyncRegDon
SEVERITY: InformationFORMAT: "RamSync Register Done error. DbID%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-DbInvalidDowngr
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-4-provItfDbRRErr
SEVERITY: ErrorFORMAT: "Error in Writing to PROV_ITF Disk for lower version plug & play port - recNum/portId%d %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This log happend during runrev from 2.x version to 3.0 or higher version. There is problem writing back to disk when provision the lower version plug&play port to disk. For each interface record failed to provision the disk, we log it as an error"RECOMMENDED ACTION: "The switch config port in lower version image can't be properly provisioned in the higher version image. Recommend you do abortrev and provision the plug&play port in lower version image before upgrade again."REQUIRED INFO: "Do dsplog -task pnRedman"REDM-7-provRRInfo_sds
SEVERITY: InformationFORMAT: "%s %d %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For information only, not an error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-provRRUpdateNum
SEVERITY: InformationFORMAT: "%s %d %d %d %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For information only"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-provRRInfo_1s2d
SEVERITY: InformationFORMAT: "%s %d %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For information only"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-provRRInfo_1s1d
SEVERITY: InformationFORMAT: "%s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For information only"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-provRRInfo_1s
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For information only"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-provLRInfo_1s
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For information only"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoREDM-7-NO_BUFFER
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "resync"
RESY-5-NOTLEAFLEG
SEVERITY: WarningFORMAT: "0x%x is not a leaf leg"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Not a leaf leg"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-LEGNULLPTR
SEVERITY: WarningFORMAT: "%s is null for a p2mp conn ifid=%ld vpi=%d vci=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Leg ptr is null for a p2mp conn"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-BLKZEROPEP
SEVERITY: WarningFORMAT: "%s RESYNC_PEP should not be on Block 0"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "RESYNC_PEP should not be on block 0"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVALIDFCNCALL
SEVERITY: WarningFORMAT: "%s This function should not have been called."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The given function should not have been called because the resync commit is complete. "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-APINULLPTR
SEVERITY: WarningFORMAT: "%s Parm %s is invalid at position %d."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was NULL."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-NULLPTR
SEVERITY: WarningFORMAT: "%s Parm %s is invalid at position %d."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Software Error. The parameter value for the named parameter acquired in named function is NULL."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-CHKSUMBLKNOMEM
SEVERITY: WarningFORMAT: "%s Failed to allocate memory. Size requested '0x%x'. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "API Software Error. An attempt to allocate a newly sized Check Sum Block Table failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-BADBLKARRNOMEM
SEVERITY: WarningFORMAT: "%s Failed to allocate memory. Size requested '0x%x'. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "API Software Error. An attempt to allocate a newly sized Bad Block Array failed."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-FREELSTNOMEM
SEVERITY: WarningFORMAT: "%s Failed to allocate memory for free list. Size '0x%x'. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "API Software Error. An attempt to allocate memory for Resync Commit List."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVCRDSTATE
SEVERITY: WarningFORMAT: "%s The card is neither an Active or Standby. %s is '0x%x'."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "We have been asked to add a connection that does not reside in either an Active or Standby Card."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-VALOUTOFRNG
SEVERITY: WarningFORMAT: "%s %s=%d != %s=%d at position %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "First value given is greater than resync's value. The system was not updated accordingly."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-CORRUPTLNKDLIST
SEVERITY: WarningFORMAT: "%s %s does not contain what we are expecting at '0x%x'. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "We are expecting a certain behaviour from the list however, the pointers examined are not what was expected Refer to code for specifics."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVMSGTYPE
SEVERITY: WarningFORMAT: "%s Expecting %s, received '0x%x'. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "We are expecting a certain message type but received another."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVCOUNTERVAL
SEVERITY: WarningFORMAT: "%s %s decremented beyond valid range, value %d. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The given counter has been decremented beyond valid range another."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-DELENTRYFAILED
SEVERITY: WarningFORMAT: "%s Delete entry call failed, return code '0x%x'. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Eitehr the list is already empty or it is corrupt."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVALIDCASE
SEVERITY: WarningFORMAT: "%s Switch on %s produced unexpected value '0x%x'. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we performed a switch on a given switch statement whose value was not expected."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INFINITELOOP
SEVERITY: WarningFORMAT: "%s Infinite Loop encountered."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we traversed a loop greater than the possible maximum for the value we are looking for."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-TIMERCREATEFAIL
SEVERITY: WarningFORMAT: "%s We failed to create a a timer."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we used SSI to create a timer which we failed at."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-TIMERSTARTFAIL
SEVERITY: WarningFORMAT: "%s We failed to start a timer. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we used SSI to start a timer which we failed at."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-TIMERDELFAIL
SEVERITY: WarningFORMAT: "%s We failed to delete a timer."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we used SSI to delete a timer which we failed at creating."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-MALLOCFAIL
SEVERITY: WarningFORMAT: "%s Failed to allocate memory of size'0x%x', memType'0x%x', Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we failed to allocate memory for the given amount and memory type."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-RELDSLVCHKSMFAI
SEVERITY: WarningFORMAT: "%s Failed to reload slave's checksum, slaveId='0x%x', RC='0x%x'."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we failed to reload check sum for the given slave."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INITSLVCHKSMFAI
SEVERITY: WarningFORMAT: "%s Failed to init slave's checksum, RC='0x%x'."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we failed to init checksum."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVALIDSLAVEID
SEVERITY: WarningFORMAT: "%s Slave Id encountered is invalid '0x%x'."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we encountered an invalid slave Id"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-UNKNOWNSTATE
SEVERITY: WarningFORMAT: "%s Given state, '0x%x', is unknown."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we are in a state we don't know how to handle, therefore we may enter an error state. "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVALIDEVENT
SEVERITY: WarningFORMAT: "%s Given event, '0x%x', is invalid in this state '0x%x'."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we are in a state where we don't know how to handle this event. "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-RCNOTOK
SEVERITY: WarningFORMAT: "%s We called %s, but it did not return OK, rc '0x%x'. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we called the given function name, however it returned the given return code."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVALIDCODEEXEC
SEVERITY: WarningFORMAT: "%s We executed a portion of code that we should not have."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we exectued a portion of code that we should not have. A bug must have been introduced in the code."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-PEPEXIST
SEVERITY: WarningFORMAT: "%s Pep already in resync database."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot add pep to the resync database. It already exists."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-PEPNOTEXIST
SEVERITY: WarningFORMAT: "%s Pep not in resync database."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot delete pep from the resync database. No such pep exists."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-GETCMTBUFFAIL
SEVERITY: WarningFORMAT: "%s vsimwGetConnCmtMsgBuf return NULL."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Fail to get buffer for connection commit message."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-GETINITCKSMBUFF
SEVERITY: WarningFORMAT: "%s vsimwGetInitChksumInfoMsgBuf return NULL."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Fail to get buffer for init checksum message."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-GETADJCKSMBUFFA
SEVERITY: WarningFORMAT: "%s vsimwGetAdjustChksumRequestMsgBuf return NULL."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Fail to get buffer for adjust checksum message."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-NOTINCMTLIST
SEVERITY: WarningFORMAT: "%s Can't delete, entry not in cmt list"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot delete, entry not in commit list"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-ALREADYFREE
SEVERITY: WarningFORMAT: "%s Can't add to free list, already freed"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot add to free list, already freed"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-WRONGSEQNUM
SEVERITY: WarningFORMAT: "%s Wrong resync seq number. seqNum=%d resyncSeqNum=%d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Wrong resync sequence number"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-LEAFNULLPTR
SEVERITY: WarningFORMAT: "%s %s is null for a scaled master conn ifid=%ld vpi=%d vci=%d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Leaf ptr is null for a scaled master conn"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-ROOTNULLPTR
SEVERITY: WarningFORMAT: "%s %s is null for a scaled slave conn ifid=%ld vpi=%d vci=%d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Root ptr is null for a scaled slave conn"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-ADDCMTLISTFAIL
SEVERITY: WarningFORMAT: "%s Can't add into commit list"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot add to commit list"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-BADVSIMMSG
SEVERITY: WarningFORMAT: "%s Bad vsim message type"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Bad vsim message type"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-MAXCHKSMBLK0
SEVERITY: WarningFORMAT: "%s maxChksmBlk or slaveId is 0,intf(0x%x)"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "maxChksmBlk or slaveId is 0"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVCHKSUMBLK
SEVERITY: WarningFORMAT: "%s vsiChksmBlk >= maxChksmBlk, vsiChksmBlk = %d, maxChksmBlk %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "vsiChksmBlk >= maxChksmBlk"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-RESIZEFAIL
SEVERITY: WarningFORMAT: "%s cannot resize checksum table"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot resize checksum table"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-ADDSLAVEFAIL
SEVERITY: WarningFORMAT: "%s cannot add %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot add slave"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-ADJSLAVEFAIL
SEVERITY: WarningFORMAT: "%s cannot adjust %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot adjust slave"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-RESYNCELEFAIL
SEVERITY: WarningFORMAT: "%s cannot alloc & init resync element"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot alloc & init resync element"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-DELELEFAIL
SEVERITY: WarningFORMAT: "%s cannot delete resync element"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Cannot delete resync element"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-BLKMISMATCH
SEVERITY: WarningFORMAT: "%s checksum block mismatch, resync blk %d blk %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Checksum block mismatch"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVRSPCODE
SEVERITY: WarningFORMAT: "%s Invalid response code for cmt rsp msg. rsp code=%d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Invalid response code for cmt response message"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-ENDRCMDFAIL
SEVERITY: WarningFORMAT: "%s Fail to send end resync cmd, fail reason %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Fail to send end resync command"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-ITFGMOREFAIL
SEVERITY: WarningFORMAT: "%s Fail to send interface getmore msg, fail reason %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Fail to send interface getmore msg"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-SECONDCMTZERO
SEVERITY: WarningFORMAT: "%s second commit counter is zero"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "second commit counter is zero"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-RESYNC_ERR
SEVERITY: WarningFORMAT: "%s %s"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "System Error in Resync"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-SLAVEEXISTS
SEVERITY: WarningFORMAT: "%s Tried to add slave,Id '0x%x', that already exists. Pos %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we attempted to add a salve entry in the resync slave table but it already exists."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-WARINFINITELOOP
SEVERITY: WarningFORMAT: "%s Infinite Loop encountered, traversed '0x%x' times."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we traversed a loop greater than the given theoretical maximum. Should this be of concern. "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-STRANGERSP
SEVERITY: WarningFORMAT: "%s Response '0x%x' with reason '0x%x'."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "In the given function, we received a REJECT or an ERROR response or NAK with a reason not to retry, while trying to commit the connection."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-LOWMEMORY
SEVERITY: WarningFORMAT: "%s System Memory is low. "FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Resync has detected low memory in the system. Therefore, it will reject the current request and return error to the caller. This avoids failure management code from kicking in."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-OUTOFRANGE
SEVERITY: WarningFORMAT: "%s %s is at %d. Its out of range. "FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Resync has accessed an internal variable that is out of expected range."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-CNTRLVCFAIL
SEVERITY: WarningFORMAT: "%s Control VC commit NACKed, VPI %d VCI %d IFid%ld. "FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Resync has received NACK for Control VC commit. "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-NAKRSP
SEVERITY: WarningFORMAT: "%s NACK response received"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Nak response received"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-INVITF
SEVERITY: WarningFORMAT: "%s Invalid %s interfaces. pri_itf %ld sec_itf %ld"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid interfaces during addPep."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-FASTCMT
SEVERITY: WarningFORMAT: "%s Fast resync commit counter is non zero when done"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Fast resync commit counter is non zero when done."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-OLISTNOTNULL
SEVERITY: WarningFORMAT: "%s pResyncOutstandingListHead is not null at position %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "pResyncOutstandingListHead is not null"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-5-BADBLKNOCONN
SEVERITY: WarningFORMAT: "%s No conn in resync db for bad blk %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "No connection in resync db for bad block"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-7-RESYNC_ENDMISMA
SEVERITY: InformationFORMAT: "%s %s %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "End resync info in Resync"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-7-RESYNCINFO
SEVERITY: InformationFORMAT: "%s %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Resync general info"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-7-CTLVCNAK
SEVERITY: InformationFORMAT: "Ctlvc %s received. Rsn Code%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: No ExplanationRECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-7-CMTINPROG
SEVERITY: InformationFORMAT: "%s Master %lx/%d/%d Slave %lx/%d/%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Commit already in progress"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-7-PORTDN
SEVERITY: InformationFORMAT: "%s interface %lx or %lx is down"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Port down"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-7-PDATATRAP
SEVERITY: InformationFORMAT: "%s %s is %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Received pdata trap for non conn commit cmd msg"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-7-FREEPDATA
SEVERITY: InformationFORMAT: "%s %s is %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Received free pdata for non conn commit cmd msg"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoRESY-7-SECONDCMTFAIL
SEVERITY: InformationFORMAT: "%s second commit fail for ifid=%ld vpi=%d vci=%d rsp code=%d reason code=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Second commit fail"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoDDTS "rpm"
RMM-4-SENDCTCTASK_ERR
SEVERITY: ErrorFORMAT: "CTC MSG send Task Error: %s."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "It could happen if either a) not able to spawn task to send CTC events b) not able to create/attach comm endpoints for the above task. This should never happen and if it happens, soft reset will happen. If it persists, contact TAC representative"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"RMM-4-SENDCTC_MSG_PRO
SEVERITY: ErrorFORMAT: "CTC Event Message Processing Error: %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error happened while processing CTC_EVENT message."RECOMMENDED ACTION: "Indicates an internal error detected by the PXM RMM module which process ctc event msg requests to send it to the SM. It needs to be analyzed by TAC and possibly by the development team."REQUIRED INFO: "Collect dsplog, dsperr information""RMM-4-SENDCTC_MSG_ALL
SEVERITY: ErrorFORMAT: "CTC Event Message Alloc Error: %s: %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error happened while processing CTC_EVENT message."RECOMMENDED ACTION: "Indicates an internal error detected by the PXM RMM module which process ctc event msg requests to send it to the SM. It needs to be analyzed by TAC and possibly by the development team."REQUIRED INFO: "Collect dsplog, dsperr information"RMM-4-SENDCTC_MSG_SEN
SEVERITY: ErrorFORMAT: "CTC Event Message Processing Error: %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error happened while processing CTC_EVENT message."RECOMMENDED ACTION: "Indicates an internal error detected by the PXM RMM module which process ctc event msg requests to send it to the SM. It needs to be analyzed by TAC and possibly by the development team."REQUIRED INFO: "Collect dsplog, dsperr information"RFS-4-NO_IPC_BUFFER
SEVERITY: ErrorFORMAT: "%s%d Could not get IPC buffer."FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Unable to get ipc buffer for communication. This might impact IPC commnunication for a while. If it still persists, this will impact the routine operations. Hence this needs to be analysed by TAC and possibly by development team."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 "ERPM"RFS-4-PORT_CREATE_ERR
SEVERITY: ErrorFORMAT: "Could not create port %s."FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Unable to create port for communication. This will impact IPC commnuication between RPM and PXM which inturn might affect routine operations. This needs to be analysed by TAC and possibly by development team."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 "ERPM"RFS-4-TASK_SPAWN_ERR
SEVERITY: ErrorFORMAT: "Could not spawn task %s."FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Unable to spawn task. In this case, rfs server failed to come up. 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: 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 "ERPM"RFS-5-REQ_DROP
SEVERITY: WarningFORMAT: "RFS request type %d DROPPED."FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "RFS request dropped. This is due to any of the following.a) Not able to get ipc buffer.b) Not able to identify the rfc request.if you see the string <rfs_server_action unsupported RFS request> in the error message, this might be a momentary event. If this happens continously or if this string is not seen, It needs to be analyzed by TAC and possibly by the development team."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 "ERPM"RFS-4-GENERIC
SEVERITY: ErrorFORMAT: "%s %s %s."FLAG: No FlagTHROTTLING: One SecondEXPLANATION: "Number of entries in the directory E/RPM are over the limit. The limit is 128."RECOMMENDED ACTION: "The number of file entries in E/RPM exceeded 128. Delete Unwanted files from this directory to reduce the count below 128."REQUIRED INFO: "No information to collect. Perform the recommended action to fix this problem."RFS-4-GEN_ERROR
SEVERITY: ErrorFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "This error will be logged due any of the following.1. Unable to open desired file from E;RPM2. Unable to get the stats of specific file3. Trying to load Invalid file which is not there in ERPM4. Unable to removed the specific file5. Invalid File Descriptor6. Unable to close the file7. Trying to remove when the file is in Use8. Unable to remove the file from Standby PXM9. Unable to rename the file10. Unable to create a directory11. Unable to remove a directory12. Unable to read the file13. Unable to write the file14. Unable to seek from the file15. File name too long when translating the device name prefix16. Failed to register RFS server port "RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRFS-5-GEN_WARNING
SEVERITY: WarningFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For logging all RFS related warnings"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRFS-6-GEN_NOTICE
SEVERITY: NoticeFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For logging all RFS related notices"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoRFS-7-GEN_INFO
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "For logging all RFS related info messages"RECOMMENDED ACTION: No action requiredREQUIRED INFO: No Required InfoDDTS : "rpmxf-cpro"
CPRO-7-CONNCAPEXCEED
SEVERITY: InformationFORMAT: "Connection capacity of card reached"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Software limit for the provisioned connection capacity has been reached. Cannot provision any more connections."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-5-NONEXISTCONN
SEVERITY: WarningFORMAT: "Connection %d.%d.%d does not exist"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Connection does not exist while an internal operation took place. This can happen under some circumstances. This event logs is reqd to keep track of those circumstances."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-4-PASSTHROREGFAIL
SEVERITY: ErrorFORMAT: "Could not register for passthrough"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "All provisioning requests for connections are bound to fail. Possible indication of VSI layer failure. Rootcause of failure can be many including internal memory leakages, IPC buffer leakages."RECOMMENDED ACTION: "Please collect the following information for further analysis and call TAC support; This may require a reboot or switchover of the SM. Before doing so, TAC may need to collect relevant information."REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-3-DOWNLOADFAIL
SEVERITY: Minor AlertFORMAT: "Error downloading from disk"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Could not download connection configuration from disk. The problem could span across several entities in AXSM/PXM. The problems could range from memory/IPC buffer leakages to runaway/suspended task on either card."RECOMMENDED ACTION: "There may not be a need for any corrective action as the card would be reset. However, please collect the following information for further analysis and call TAC"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-7-SYNCRAMERR
SEVERITY: InformationFORMAT: "Sync Ram Error at line %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal Error. Could occur under normal circumstances. Typical scenario includes reset of standby AXSM while bulk/incremental sync is in progress"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-4-DBMINITFAIL
SEVERITY: ErrorFORMAT: "Error registering with DB manager"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "DB server did not accept registration from AXSM. The problem could span across several entities in AXSM/PXM. The problems could range from memory/IPC buffer leakages to runaway/suspended task on either card."RECOMMENDED ACTION: "There may not be a need for any corrective action as the card would be reset. However, please collect the following information for further analysis and call TAC"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-4-CPROTIMERFAIL
SEVERITY: ErrorFORMAT: "Could not start cPro timer"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Internal error with card infrastructure. Will impact connection alarm integration and reporting activity."RECOMMENDED ACTION: "In all probability, the card would reset. Regardless of this, please collect the following information for further analysis and call TAC"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-4-CPROMSGHDLRFAIL
SEVERITY: ErrorFORMAT: "Error attaching cPro msg handler; errno = %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Internal error with card infrastructure. The card would eventually reset."RECOMMENDED ACTION: "There may not be a need for any corrective action as the card would be reset. However, please collect the following information for further analysis and call TAC"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-4-INVALID_CNTRLR_
SEVERITY: ErrorFORMAT: "Error in retrieving controller information"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error in retrieving controller information from shelf management database. May affect all connection provisioning activity on the card."RECOMMENDED ACTION: "Please collect the following information for further analysis and call TAC support; This may require a reboot or switchover of the SM/PXM. Before doing so, TAC may need to collect relevant information."REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-4-SYNCRAMINITFAIL
SEVERITY: ErrorFORMAT: "line %d: Ram Sync %s error - errno = 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal error with card infrastructure. The card would eventually reset."RECOMMENDED ACTION: "There may not be a need for any corrective action as the card would be reset. However, please collect the following information for further analysis and call TAC"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-4-ALRM_REG_FAIL
SEVERITY: ErrorFORMAT: "Error registering with Card alarm manager"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error registering with Card alarm manager. Alarm reporting for conns is disabled."RECOMMENDED ACTION: "Please collect following information before contacting TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-3-MISMATCH_CONN
SEVERITY: Minor AlertFORMAT: "Mismatch on connection %d.%d.%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Mismatch between SPVC manager and AXSM databases for this connection. This could happen because of PXM45/AXSM switchover while provisioning or possible database update failures at either end."RECOMMENDED ACTION: "Check if the connection is still in this condition, using the dspcons command on AXSM. If it is not, then this is a possible transient condition and can be ignored. If condition does exist, then attempt to rectify the problem with following steps:a) If this is a master endpoint, attempt toadmin down and up the connection.b) If this is a slave endpoint, then deleteand readd the whole connection. If either of them, does not help please collect the following info and inform TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-7-RINGCONGESTION
SEVERITY: InformationFORMAT: "Ring Congested; Wr:%d Rd:%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Ring Congested."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-7-RINGCONGABATE
SEVERITY: InformationFORMAT: "Ring Congestion Abate; Wr:%d Rd:%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Ring Congestion Abate."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-6-UNKNOWN_MSGTYPE
SEVERITY: NoticeFORMAT: "Unknown message type %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unknown message type "RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-3-FLUSHFAIL
SEVERITY: Minor AlertFORMAT: "Error flushing semaphore; errno=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal error in card infrastructure. This may not result in a catastrophic failure, but it is probably indicative of a basic problem in the SSI."RECOMMENDED ACTION: "User may need to switchover to a redundant card, if there is one. However, before doing so, it is advisable to collect the following information and involve TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-3-AVLFAIL
SEVERITY: Minor AlertFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal error in AVL library functions. This may cause problems over a period of time."RECOMMENDED ACTION: "User may need to switchover to a redundant card, if there is one. However, before doing so, it is advisable to collect the following information and involve TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-3-CONNDB_ERR
SEVERITY: Minor AlertFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal connection database error. May result in problems over a period of time."RECOMMENDED ACTION: "User may need to switchover to a redundant card, if there is one. However, before doing so, it is advisable to collect the following information and involve TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) Coredump if the card had resetCPRO-7-CANNOT_FIND_REC
SEVERITY: InformationFORMAT: "Could not find record for %d.%d.%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "None"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-7-CPROTASK
SEVERITY: InformationFORMAT: "%s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid CTC transition prevented"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-7-CHKSUM_MISMATCH
SEVERITY: InformationFORMAT: "Checksum mismatch in Record %d: disk %d record %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Check mismatch between disk & RAM database detected during resync which occurs on a standby to active role transition. This is a normal event that was possibly caused by transient card events at the time when provisioning was done."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-5-NONEXISTOPSTATE
SEVERITY: WarningFORMAT: "EM OpState invalid for ifNum %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Events introduced to guard against possible API failures. These failures usually result in basic loss of functionality and detected during the development testing or regression testing cycles."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-5-EMGETOPSTATEFAI
SEVERITY: WarningFORMAT: "EM Get OpState fails for ifNum=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Events introduced to guard against possible API failures. These failures usually result in basic loss of functionality and detected during the development testing or regression testing cycles."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-5-NONEXISTADMSTAT
SEVERITY: WarningFORMAT: "EM AdmState invalid for ifNum %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Events introduced to guard against possible API failures. These failures usually result in basic loss of functionality and detected during the development testing or regression testing cycles."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-5-EMGETADMSTATEFA
SEVERITY: WarningFORMAT: "EM Get AdmState fails for ifNum %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Events introduced to guard against possible API failures. These failures usually result in basic loss of functionality and detected during the development testing or regression testing cycles."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-5-GETOPSTATEFAIL
SEVERITY: WarningFORMAT: "cPro Get OpState fails for ifNum %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Events introduced to guard against possible API failures. These failures usually result in basic loss of functionality and detected during the development testing or regression testing cycles."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-5-GETADMSTATEFAIL
SEVERITY: WarningFORMAT: "cPro Get AdmState fails for ifNum %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Events introduced to guard against possible API failures. These failures usually result in basic loss of functionality and detected during the development testing or regression testing cycles."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-4-ADDCHANLOOPFAIL
SEVERITY: ErrorFORMAT: "cPro Addchanloop fails. ifNum=%d, vpi=%d, vci=%d, dir=%d."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal error while attempting to add chan loopback. This will not impact the regular functioning of the card. However, this needs to be analysed by engineering."RECOMMENDED ACTION: "Please collect the following details and inform TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) dspconinfo on PXMh) dsppnports on PXMi) dsplns on AXSMh) dspports on AXSMh) dspspvcifs on AXSMh) dspcon on AXSMCPRO-7-DELCHANLOOPFAIL
SEVERITY: InformationFORMAT: "cPro Delchanloop fails. ifNum=%d, vpi=%d, vci=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal error while attempting to add chan loopback. This will not impact the regular functioning of the card. However, this needs to be analysed by engineering."RECOMMENDED ACTION: "Please collect the following details and inform TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) dspconinfo on PXMh) dsppnports on PXMi) dsplns on AXSMh) dspports on AXSMh) dspspvcifs on AXSMh) dspcon on AXSMCPRO-4-NULLRSPPTR
SEVERITY: ErrorFORMAT: "Null response ptr is returned"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal IPC error in the card. This will not affect regular functioning of the card. However, this problem needs to be analysed by TAC/engineering: "RECOMMENDED ACTION: "Please collect the following details and inform TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) dspconinfo on PXMh) dsppnports on PXMi) dsplns on AXSMh) dspports on AXSMh) dspspvcifs on AXSMh) dspcon on AXSMCPRO-4-IPCMSGALLOCFAIL
SEVERITY: ErrorFORMAT: "IPC Message Allocation failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal IPC error in the card. This will not affect regular functioning of the card. However, this problem needs to be analysed by TAC/engineering: "RECOMMENDED ACTION: "Please collect the following details and inform TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) dspconinfo on PXMh) dsppnports on PXMi) dsplns on AXSMh) dspports on AXSMh) dspspvcifs on AXSMh) dspcon on AXSMrther analysis. DE may want to investigate on live system. Pls DO NOT reset/switchover to redundant card"CPRO-7-IPCMSGSENDSYNCF
SEVERITY: InformationFORMAT: "IPC Message SendSync failed"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Internal IPC error in the card. This will not affect regular functioning of the card. However, this problem needs to be analysed by TAC/engineering: "RECOMMENDED ACTION: "Please collect the following details and inform TAC:"REQUIRED INFO: a) dspcds on PXMb) dspred on PXMc) dspcd <slot> on PXMd) dspcd on the affected slote) dsprevs on PXMf) All event logs prior to event (dsplog)g) All error logs prior to event (dsperr)h) dspconinfo on PXMh) dsppnports on PXMi) dsplns on AXSMh) dspports on AXSMh) dspspvcifs on AXSMh) dspcon on AXSMCPRO-7-RECFOUNDNOTLPBK
SEVERITY: InformationFORMAT: "Connection not in loopback. ifNum=%d, vpi=%d, vci=%d, dir=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "User is attempting to delete loopback on a connection which is not in loopback."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-7-DALDSPCONNLOOPE
SEVERITY: InformationFORMAT: "dalDspConnLoop(ifNum=%d) return ERROR."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "dalDspConnLoop() return ERROR."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-7-DSPCHANLOOPFAIL
SEVERITY: InformationFORMAT: "cPro Dspchanloop fails. ifNum=%d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "cPro Dspchanloop fails."RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoCPRO-7-SNMP_ERROR
SEVERITY: InformationFORMAT: "SNMP error; id = %d; err : %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "SNMP get/set operation fails."RECOMMENDED ACTION: "This error is also displayed on CWM. So, there is no need to take any action on switch side."REQUIRED INFO: No Required InfoCPRO-4-RAMDISK_ERR
SEVERITY: ErrorFORMAT: "RamDisk error : %s; errno=%d\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Alarm file RamDisk operation error."RECOMMENDED ACTION: "Please collect the following info and contact TAC"REQUIRED INFO: "From PXM45 :1) dspdate2) dsplog for this slot3) dspver"CPRO-7-HOT_STDBY
SEVERITY: InformationFORMAT: "dsphotstandby cmd : %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "error while executing dsphotstandby command."RECOMMENDED ACTION: "This is an info message."REQUIRED INFO: No Required InfoCPRO-7-GEN_INFO
SEVERITY: InformationFORMAT: "%s; %d, errno=%d\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "general cpro health related info"RECOMMENDED ACTION: "This is an Info"REQUIRED INFO: No Required InfoCPRO-4-TRANSACTION_ERR
SEVERITY: ErrorFORMAT: "connection Transaction err : %s; errno=%d\n"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "error happened when getting/incrementing transaction id."RECOMMENDED ACTION: "Please collect the following info and contact TAC"REQUIRED INFO: "From PXM45 :1) dspdate2) dsplog for this slot3) dspverFROM SM :1) dspcons2) from the axsm shell cProTransactionHelp "CPRO-4-GENERR
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from CPRO Module."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 requiredCPRO-4-GENERR_NUM
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>, info = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from CPRO task (with extra numbers debug info)."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 requiredCPRO-4-GENERR_NUM2
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>, info = %d %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from CPRO task (with extra numbers debug info)."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 requiredCPRO-4-GENERR_STR
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>, info = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from CPRO task (with extra string debug info)."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 requiredCPRO-2-CNTLRLIST
SEVERITY: Major AlertFORMAT: "%s, line %d: <%s>"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An error has occured in getting the list of controllers from the PXM. SPVC config commands will not be successful on this card"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 requiredCPRO-4-PASSTHRUFAIL
SEVERITY: ErrorFORMAT: "%s, line %d: Passthru Reg failed for the controller = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An error has occured in registering the controller with the vsi slave. If the conntroller is a PNNI controller, the SPVC config commands will not be successful on this card"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 requiredCPRO-4-COMEPCREATEFAIL
SEVERITY: ErrorFORMAT: "%s, line %d: Endpoints creation failed cProEpId=%x iLmiEpId=%x cProCtcEpId=%x cProCdRoleEpId=%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An error has occured in creating the CPRO endpoints. CPRO will not be able to receive any messages."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 requiredCPRO-4-MSGHDLRATCHFAIL
SEVERITY: ErrorFORMAT: "%s, line %d: Message handler attach failed for %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An error has occured in attaching the message handler to the endpoint. CPRO will not be able to receive any messages on this 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 requiredCPRO-4-BULKCNFGFAIL
SEVERITY: ErrorFORMAT: "%s, line %d: Failure sending rsprtn info to vsis for partn = %d, returned error = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A error has occured in sending the resource partition information to the vsi slave"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 requiredCPRO-7-UNKNWNMSGTYP
SEVERITY: InformationFORMAT: "%s, line %d: Unknown message type = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An unknown message type has been received and dumped"RECOMMENDED ACTION: "This is an info"REQUIRED INFO: No Required InfoRESY-7-CONNSYNCHFAIL
SEVERITY: InformationFORMAT: "%s, line %d: Err in conn synch with vsim: error = 0x%x, vpi = %d, vci = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "An error has occured while performing connection DB resynch with the PNNI controller"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 requiredRESY-4-GENERR
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from the Connection RESYNCH Module."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 requiredCMM_-4-GENERR
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from the Connection CLI."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 requiredCMM_-4-GENERR_NUM
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>, info = %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from the Connection CLI(with extra number debug info)."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 requiredCMM_-4-GENERR_NUM2
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>, info = %d %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from the Connection CLI (with extra numbers debug info)."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 requiredCMM_-4-GENERR_NUM3
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>, vpi.vci = %d.%d, error = 0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from the Connection CLI (with extra numbers debug info)."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 requiredCMM_-4-GENERR_NUM4
SEVERITY: ErrorFORMAT: "%s, line %d: <%s>, vpi.vci = %d.%d, error = 0x%x err str = %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "General Error messages from the Connection CLI (with extra numbers debug info)."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 : "rpmxf-ssi"
FIPC-5-WARNING
SEVERITY: WarningFORMAT: "Where: %s()::%d, Errno: 0x%x, ErrMsg: %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "FIPC warning: func()::line, Errno, Error Msg"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-7-INFO
SEVERITY: InformationFORMAT: "Where: %s()::%d, Errno: 0x%x, ErrMsg: %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "FIPC info: func()::line, Errno, Error Msg"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-COMEPSEMTAKE
SEVERITY: ErrorFORMAT: "%s, line %d, Error %x taking FIPC semaphore %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Error while acquiring EPID semaphore"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.FIPC-5-ISRNOTCALLABLE
SEVERITY: WarningFORMAT: "%s, line %d, Attempt to take FIPC semaphore %x from interrupt routine"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Attempt to take FIPC semaphore from an interrupt routine"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-MCASTPSLOTINVAL
SEVERITY: WarningFORMAT: "%s:Invalid Physical Slot number %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Physical slot number is invalid"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-MCASTPORTINVAL
SEVERITY: WarningFORMAT: "%s:Multicast not support on port %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Multicast is not supported for this port"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-COMEPMALLOCERR
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to alloc mem for CommEp array (lstSize %d, arraySize %d)"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to alloc mem for CommEp array"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.FIPC-4-NUMCOMEPINVALID
SEVERITY: ErrorFORMAT: "%s, line %d, Desired number of Comm Eps %d exceeds the system limit %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Number of EPID's exceeded in the system"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.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.FIPC-4-COMEPMEMAREAERR
SEVERITY: ErrorFORMAT: "%s, line %d, Insufficient memory for Comm Ep array: Want %d, %d; Got %d, %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Insufficient memory for Comm Ep array"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.FIPC-5-COMEPALLOCFAIL
SEVERITY: WarningFORMAT: "%s, line %d, Failed to allocate an FIPC Comm. endpoint at %p"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to allocate an FIPC communications Endpoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-COMEPFREEFAIL
SEVERITY: WarningFORMAT: "%s, line %d, Failed to free an FIPC Comm Endpoint %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to free an FIPC communications Endpoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-COMEPIDINVALID
SEVERITY: WarningFORMAT: "%s, line %d, An invalid FIPC_COM_EPID of %p was passed as an argument."FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "An invalid FIPC Communications Endpoint Id was passes"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.FIPC-5-COMEPDELETED
SEVERITY: WarningFORMAT: "%s, line %d, Non-existing CommEp %p has invalid tag %p; Expected tag is %p."FLAG: No FlagTHROTTLING: One TickEXPLANATION: "A non-existing communications Endpoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-COMEPOWNERINVAL
SEVERITY: WarningFORMAT: "%s, line %d, Communication Endpoint %x: access by non-owner task"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Communication Endpoint being accessed by non-owner task"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-COMEPTYPEINVAL
SEVERITY: WarningFORMAT: "%s, line %d, Communication Endpoint %x: invalid type %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Communication Endpoint not IPC plain Async EndPoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-COMEPSEMINVALID
SEVERITY: ErrorFORMAT: "%s, line %d, Invalid semaphore %p in Comm Ep %p"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Invalid semaphore in a Communications Endpoint"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error 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.FIPC-4-COMEPNAMEINVAL
SEVERITY: ErrorFORMAT: "%s, line %d, Communication Endpoint's %x global name %s too long"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Communication Endpoint's global name is too long"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.FIPC-5-COMEPNAMESCOINV
SEVERITY: WarningFORMAT: "%s, line %d, Name Scope %d is invalid"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Communication Endpoint NameScope invalid"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-COMEPRPLYEPDINV
SEVERITY: ErrorFORMAT: "%s, line %d, Couldn't get task's Sync Rply Epid, errno %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Couldn't get Task's Sync Reply 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: 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.FIPC-5-EPHNDLRFAIL
SEVERITY: WarningFORMAT: "%s, line %d, FIPC EPHandler %x on Ep %x returning errno %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "FIPC Endpoint handler returned error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-EPHNDLRATTACHED
SEVERITY: WarningFORMAT: "%s, line %d, Com Ep %x already has EP Handler attached"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Communication Endpoint is already attached"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-EPWAITEXTINVPRM
SEVERITY: WarningFORMAT: "%s, line %d, Status parameter %x to ssiIpcComEpWaitExit is invalid"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "ssiIpcComEpWaitExit received an invalid status parameter"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-SYNCCTXTINUSE
SEVERITY: WarningFORMAT: "%s, line %d, Sync context in use in Comm Epid %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Sync Context is already in use for this EPID"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-SYNCCTXTCLNERR
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to cleanup sync context for epid %x, errno %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to cleanup sync context for 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: 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.FIPC-5-SYNCINVALIDRPLY
SEVERITY: WarningFORMAT: "%s, line %d, Invalid sync reply on epid %s, Epid %x (%x), SeqNum %d (%d)"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid sync reply on an Endpoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-SYNCNOTSYNCRPLY
SEVERITY: WarningFORMAT: "%s, line %d, Received msg not Sync Reply on epid %s"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Received message is not a Sync reply on the endpoint"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-MSGQDELETEFAIL
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to delete FIPC message queue, queue %x, errno %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Failed to delete FIPC message queue"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.FIPC-4-MSGQCREATEFAIL
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to create FIPC message queue, error %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to create FIPC message queue"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.FIPC-4-MSGQDEAD
SEVERITY: ErrorFORMAT: "%s, line %d, FIPC message queue, queue %x is dead"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "FIPC message queue is dead"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.FIPC-4-HIGHMSGQDEAD
SEVERITY: ErrorFORMAT: "%s, line %d, FIPC message High queue, queue %x is dead"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "FIPC message High Queue Dead"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.FIPC-4-LOWMSGQDEAD
SEVERITY: ErrorFORMAT: "%s, line %d, FIPC message Low queue, queue %x is dead"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "FIPC message Low Queue Dead"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.FIPC-4-MSGQEVENT
SEVERITY: ErrorFORMAT: "%s, line %d, FIPC MsgQ Event: %s, queue %x, parameters %x, %x, %x, %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Message Queue Event Occurred"RECOMMENDED ACTION: "No action required. This is just an event occurred in the msg Queue"REQUIRED INFO: No Required InfoFIPC-4-RETXQSIGLCKFAIL
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to lock timer signal, errno %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Failed to lock timer signal"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.FIPC-4-RETXQSGUNLKFAIL
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to unlock timer signal, errno %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Failed to unlock timer signal"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.FIPC-5-RETXQMQCHAINERR
SEVERITY: WarningFORMAT: "%s, line %d, %s, Retxq %x Got %x, Expected %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Message not the first msg in the chain"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-RETXQTIMERSET
SEVERITY: WarningFORMAT: "%s, line %d, RetxQ %x: timer set error %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Retransmission queue time set error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-RETXQTIMRCANCEL
SEVERITY: WarningFORMAT: "%s, line %d, RetxQ %x: timer cancel error %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Retransmission queue timer cancel error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-MBLKMPOOLCRTERR
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to create FIPC mblk pool (tot. mblks %d, fltg. mblks %d)"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to create FIPC mblk pool"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.FIPC-4-MBLKBPOOLCRTERR
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to create FIPC buffer pool(buf size %d, num bufs %d)"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Failed to create FIPC buffer pool"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.FIPC-4-MBLKBUFDESCERR
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to alloc FIPC buffer descriptor memory (num buf desc %d)"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Failed to allocate FIPC 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.FIPC-5-DBUFSIZEINVALID
SEVERITY: WarningFORMAT: "%s, line %d, Requested data buffer size %d exceeds system max buffer size"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Requested data buffer size exceeds the system max buf size"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-MBLKALLOCFTLERR
SEVERITY: ErrorFORMAT: "%s, line %d, Fatal error %x allocating floating mblk, mblk control corrupted "FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Fatal error while allocating floating mblk, mblk, control corrupted"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.FIPC-4-MBLKINVALID
SEVERITY: ErrorFORMAT: "%s, line %d, Invalid message descriptor"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Invalid message descriptor"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.FIPC-4-MBLKASSIGNFAIL
SEVERITY: ErrorFORMAT: "%s, line %d, Message assignment failed: %s %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Message assignment 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.FIPC-5-MBLKUNAVAILABLE
SEVERITY: WarningFORMAT: "%s, line %d, No mblk available for a buffer - mblk pool corrupted"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "No mblk available for a buffer - mblk pool corrupted"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-MBLKENQUEUED
SEVERITY: WarningFORMAT: "%s, line %d, Epid %x; Msg %x already enqueued, next %x, datap %x, owner %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Memory block is already enqueued and in use"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-MBLKNOHDRSPACE
SEVERITY: ErrorFORMAT: "%s, line %d, No space for header, errno %x, Wanted %d, Got %d"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "No space for header"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.FIPC-4-MBLKBUFFREEFAIL
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to free data buffer %x, errno %x"FLAG: No FlagTHROTTLING: 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.FIPC-4-MBLKFREEFAIL
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to free mblk %x, errno %x"FLAG: No FlagTHROTTLING: 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.FIPC-4-BUFSZERR
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to get padding size for chunk data size %d, errno %x"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "The padding size could not be determined for the given chunk data size. This is an internal 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: 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.FIPC-5-LINKINERROR
SEVERITY: WarningFORMAT: "%s, line %d, FIPC Link rcv error %x, link %x; Expected %x, Got %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "FIPC link receive error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-LINKOUTERROR
SEVERITY: WarningFORMAT: "%s, line %d, FIPC Link snd error %x; Expected %x, Got %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "FIPC link send error"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-LINKMEMALLOCERR
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to allocate memory for link cfg table (num links %d)"FLAG: Stack TraceTHROTTLING: One TickEXPLANATION: "Failed to allocate memory for link config table"RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.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.FIPC-5-LINKSARREGERROR
SEVERITY: WarningFORMAT: "%s, line %d, %d: Error %x registering link %d (slot %d) lcn=0x%x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error encountered in registering link"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-LINKPLFMSLOT2RX
SEVERITY: WarningFORMAT: "%s, line %d, Platform cannot translate RxLcn for slot %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Platform cannot translate the receive LCN"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-SMSLOTERROR
SEVERITY: WarningFORMAT: "%s, line %d, Error %x and SM slot no passed is %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error encountered for the specified SM slot"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLDUPMSGFAIL
SEVERITY: WarningFORMAT: "%s, line %d, Error %x duplicating message"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error encountered in duplicating the message"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLALLOCMSGFAIL
SEVERITY: WarningFORMAT: "%s, line %d, Error %x allocating message"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error encountered in allocating the message"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-CTLRCVEPIDERR
SEVERITY: ErrorFORMAT: "%s, line %d, Error getting caller task's Receive Sync Epid"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error encountered in getting the caller task's receive Sync Endpoint Id"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.FIPC-4-CTLCOMEPERR
SEVERITY: ErrorFORMAT: "%s, line %d, Error %x instantiating FIPC Control Port"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error instantiating FIPC control port"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.FIPC-4-CTLSYNCTMRERR
SEVERITY: ErrorFORMAT: "%s, line %d, Error %x initializing FIPC Sync Timer"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error initializing FIPC sync 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: 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.FIPC-4-CTLRETXQERR
SEVERITY: ErrorFORMAT: "%s, line %d, Error %x initializing FIPC Retransmission Queue"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error Initializing FIPC retransmission queue"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.FIPC-4-CTLHDLRATTCHERR
SEVERITY: ErrorFORMAT: "%s, line %d, Error %x attaching EP Wait handler to IPC Ctl queue"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error attaching EP wait handler to IPC ctl queue"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.FIPC-4-CTLEPWAITERR
SEVERITY: ErrorFORMAT: "%s, line %d, Error %x exiting from EP Wait handler"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error exiting from EP wait handler"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.FIPC-5-CTLINVMSGTYPE
SEVERITY: WarningFORMAT: "%s, line %d, Invalid FIPC Ctl msg type %x, arg %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid FIPC control message type"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLINVMSGVER
SEVERITY: WarningFORMAT: "%s, line %d, Invalid FIPC Control msg version %x, arg %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid FIPC control message version"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLRCVMSGERR
SEVERITY: WarningFORMAT: "%s, line %d, Error %x receiving FIPC Ctl message"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error encountered in receiving FIPC control message"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLTSKCREATEERR
SEVERITY: WarningFORMAT: "%s, line %d, Error %x creating FIPC Control Task"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error encountered in creating FIPC control task"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-RSLVACKERR
SEVERITY: WarningFORMAT: "%s, line %d, Received msg %x instead of RESOLVE ACK, arg %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Received message instead of Resolve Ack"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-RSLVNAMELENERR
SEVERITY: WarningFORMAT: "%s, line %d, Requested FIPC Global Name \"%s\" too long (max name len %d )"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Name to be resolved too long"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLOUTOFMBLKS
SEVERITY: WarningFORMAT: "%s, line %d, FIPC Control could not allocate mblk"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "FIPC control could not allocate memory block"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLBINDSTUNKN1
SEVERITY: WarningFORMAT: "%s, line %d, Epid %x: Bind st. unknown, error %x sending duped BIND Rqst"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unknown error encountered while sending duped BIND request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLBINDSTUNKN2
SEVERITY: WarningFORMAT: "%s, line %d, Epid %x: Bind state unknown, error %x receiving BIND Ack"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unknown Bind state while receiving BIND Ack"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLBINDSTUNKN3
SEVERITY: WarningFORMAT: "%s, line %d, Epid %x: Bind state unknown, error %x putting BIND Rqst on RetxQ"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unknown Bind state while putting BIND request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLBINDSTUNKN4
SEVERITY: WarningFORMAT: "%s, line %d, Epid %x: Bind st unknown, unknown sts %x in BIND Ack, errno %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unknown Bind state in BIND Ack"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-5-CTLBINDSTUNKN5
SEVERITY: WarningFORMAT: "%s, line %d, Epid %x: Bind state unknown, error %x retransmitting BIND Rqst"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unknown Bind state while retransmitting BIND request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-CTLBINDSTFAIL1
SEVERITY: ErrorFORMAT: "%s, line %d, Epid %x: Bind state failed, error %x sending to Name Svr"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Bind request failed because of error while sending to Name server"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.FIPC-4-CTLBINDSTFAIL2
SEVERITY: ErrorFORMAT: "%s, line %d, Epid %x: Bind state failed, error %x - out of mblks"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Bind state failed due to an outage of memory blocks"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.FIPC-4-CTLBINDSTFAIL3
SEVERITY: ErrorFORMAT: "%s, line %d, Epid %x: error %x binding global name"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Bind request failed because it was invalid"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.FIPC-4-CTLUNBINDSTFAIL
SEVERITY: ErrorFORMAT: "%s, line %d, Epid %x: UnBind state failed, error %x sending to Name Svr"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Error in unbind because of send request failed to Name server"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.FIPC-5-CTLUNBINDSTUNKN
SEVERITY: WarningFORMAT: "%s, line %d, Epid %x: UnBind st. unknown, error %x sending duped UNBIND Rqst"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Unknown Unbind state while sending duped UNBIND request"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-CTLMAXBUFRPLYER
SEVERITY: ErrorFORMAT: "%s, line %d, Error in Replying to Query for MaxBufSize, error %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Reply to Remote Card Query for Buffer Size 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.FIPC-4-CTLINVIPCVER
SEVERITY: ErrorFORMAT: "%s, line %d, Ipc Version of Remote Card %d is different"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Message to Remote Card failed, different IPC version"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.FIPC-4-CTLINVRMTCTLMSG
SEVERITY: ErrorFORMAT: "%s, line %d, Remote Card IPC CtlMsg Version Invalid"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Message to Remote Card failed, diff IPC Ctl version"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.FIPC-4-NAMEMEMALLOC
SEVERITY: ErrorFORMAT: "%s, line %d, Failed allocate memory for %s, maxNumNames %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to allocate memory for global name array"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.FIPC-4-NAMESRCSLOTINV
SEVERITY: ErrorFORMAT: "%s, line %d, Name Server BIND Rqst from slot %d: Epid's srcPhySlotId %d"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Bind request invalid because of slot 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.FIPC-4-NAMETASKCREATE
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to create Name Server task, errno %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to create Name Server 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: 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.FIPC-4-NAMECOMEPCREATE
SEVERITY: ErrorFORMAT: "%s, line %d, Failed to instantiate name Server Comm endpoint, errno %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Failed to instantiate name server comm 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: 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.FIPC-5-NAMEINVMSGTYPE
SEVERITY: WarningFORMAT: "%s, line %d, Invalid message type %x, arg %x"FLAG: No FlagTHROTTLING: One TickEXPLANATION: "Invalid IPC ctl message type"RECOMMENDED ACTION: No Recommended ActionREQUIRED INFO: No Required InfoFIPC-4-NAMEINVMSGVER
SEVERITY: Error