MGX and SES Error Messages, Release 4
MGX and SES Error Messages, Release 4 (part B3)
Downloads: This chapterpdf (PDF - 800.0KB) The complete bookPDF (PDF - 18.8MB) | Feedback

DAL-2-DAL_INIT_ERR_ST

Table Of Contents

DAL-2-DAL_INIT_ERR_ST

DAL-4-DAL_ERR

DAL-4-DAL_ERR_STR

DAL-5-DAL_WARNING

DAL-5-DAL_WARNING_STR

DAL-7-DAL_INFO

DDTS "pxm-diag"

PXMD-4-ERR

DDTS "pxm1e"

EM-4-EM_ERROR

EM-7-EM_EVENT

EM-2-NOVRAM_READ_ERR

EM-2-LINE_HARDWARE_E

EM-2-DAUGHTER_CARD_M

EM-2-PRTSTAT

DDTS "ccma"

OAM-7-LOG

OAM-4-ERROR

DDTS "pxm-diag"

PXM4-4-ERR

DDTS "ccma"

QE48-5-QE48ERR

QE48-5-QE48ERR2

DDTS "ccma"

QE48-5-QE48SARERR

DDTS "drivers"

QE-4-FAIL2REFRESH

QE-4-EXPMANTISAFAIL

QE-5-UNKNOWNINT

QE-5-ERRINTERRUPT

QE-4-QE_ERR

QE-5-QE_ERR_STR

DDTS "drivers"

QE12-4-QESAR_ERR

QE12-5-QESAR_WARN

QE12-7-QESAR_INFO

DDTS "shm"

RED-7-MSGQSEND

RED-7-GENERAL

RED-7-INFORM

RED-7-MEMCORRT

RED-7-TIMEOUT

RED-7-WRONGMSG

RED-7-DNLDERR

RED-7-UPLDERR

DDTS "red"

REDM-7-CR_ERR

REDM-7-P2P_ADD_FAIL

REDM-7-P2P_DEL_FAIL

REDM-7-P2MP_ADD_FAIL

REDM-7-P2MP_DROP_FAIL

REDM-7-INVALID

REDM-7-NULL_PTR

REDM-7-MALLOC_ERR

REDM-7-pRedmanInitErr

REDM-7-pRedmanStdbySnd

REDM-7-pRedmanIovErr

REDM-7-pRedmanIpcSndEr

REDM-7-pRedmanMallocEr

REDM-7-pRedmanIpcMallo

REDM-7-pRedmanInValidS

REDM-7-pRedmanInValidE

REDM-7-pRedmanInfo

REDM-6-pRedmanNotice

REDM-7-pRedmanPrintDVa

REDM-7-pRedmanPrintXVa

REDM-7-pRedmanError

REDM-7-prErrStk_1s1d

REDM-7-prErrStk_1s2d

REDM-7-prErrStk_1s3d

REDM-7-ErrorStk_1s4d

REDM-7-prErr_1s1d

REDM-7-prErr_1s2d

REDM-7-prErr_1s3d

REDM-7-prErr_1s4d

REDM-7-pRedmanInfo1

REDM-7-pRedmanRootMsg

REDM-7-pRedmanTblReadE

REDM-7-pRedmanSwCnfErr

REDM-7-pRedmanInvalidR

REDM-7-pRedmanMaxLimit

REDM-7-pRedmanMap

REDM-7-pRedmanMapErr

REDM-7-pRedmanDiskRetr

REDM-7-pRedmanStdByRet

REDM-7-pRedmanRecNo

REDM-7-pRedmanMaxRec

REDM-7-pRedmanitfDsp

REDM-7-pRedmanIfCbErr

REDM-7-pRedmanItfMapEr

REDM-7-pRedmanDiskErr

REDM-7-pRedmanPepDsp

REDM-7-pRedmanPepMapEr

REDM-7-pRedmanPepMap

REDM-7-prAuditErr_1s

REDM-7-prAuditInfo_1s

REDM-7-prAuditErr_2s

REDM-7-prAuditInfo_2s

REDM-7-prAuditErr_3s

REDM-7-prAuditInfo_3s

REDM-7-prAuditErr_1s1d

REDM-7-prAuditInfo_1s1

REDM-7-prAuditErr_1s2d

REDM-7-prAuditInfo_1s2

REDM-7-prAuditErr_1s3d

REDM-7-prAuditInfo_1s3

REDM-7-prAuditErr_2s1d

REDM-7-prAuditInfo_2s1

REDM-7-prAuditErr_2s1d

REDM-7-prAuditInfo_2s1

REDM-7-prAuditErr_3s1d

REDM-7-prAuditInfo_3s1

REDM-6-RmMainLoopExit

REDM-6-RmProotMsgError

REDM-7-RmStandbyUpdtRe

REDM-7-CrJTimerErr

REDM-7-RmProotMsgProcE

REDM-7-RmInternalError

REDM-7-RmMissingProotS

REDM-7-RmActiveMsgProc

REDM-7-RmStandbyUpdtRe

REDM-7-RmStandbyUpdtPr

REDM-7-RmStandbyUpdtPr

REDM-7-RmIpcEpCreateEr

REDM-7-RmIpcEpResolveE

REDM-7-RmIpcMsgAllocEr

REDM-7-RmIpcSendMsgErr

REDM-7-CrJTimerSchErr

REDM-7-CrJTimerCancelE

REDM-7-RmInvalidEvent

REDM-7-RmInvalidEventI

REDM-7-RmRamSyncErr

REDM-7-RmIovAddErr

REDM-6-RmActiveToStand

REDM-6-RmStandbyToActi

REDM-6-RmRamDbReset

REDM-6-RmRemoteUnReg

REDM-6-RmCardRoleChang

REDM-7-RmFuncTrace

REDM-7-CrJDBInitErr

REDM-7-CrInvalidNewSta

REDM-7-CrJDBRebuildErr

REDM-7-CrJDBChkPtDelRe

REDM-6-CrNewState

REDM-6-CrCongestionOnO

REDM-5-CrRebuildIfCbNo

REDM-5-CrRebuildRootTr

REDM-5-CrRebuildSvcTre

REDM-7-CrRebuildCallRe

REDM-7-print3

REDM-7-print4

REDM-7-print5

REDM-7-print1s5d

REDM-7-pRedmanRevChgRe

REDM-7-pRedmanRevRegDo

REDM-7-pRedmanMaxAccIn

REDM-7-RmRamSyncRevChg

REDM-7-RmRamSyncRegDon

REDM-7-DbInvalidDowngr

REDM-4-provItfDbRRErr

REDM-7-provRRInfo_sds

REDM-7-provRRUpdateNum

REDM-7-provRRInfo_1s2d

REDM-7-provRRInfo_1s1d

REDM-7-provRRInfo_1s

REDM-7-provLRInfo_1s

REDM-7-NO_BUFFER

DDTS "resync"

RESY-5-NOTLEAFLEG

RESY-5-LEGNULLPTR

RESY-5-BLKZEROPEP

RESY-5-INVALIDFCNCALL

RESY-5-APINULLPTR

RESY-5-NULLPTR

RESY-5-CHKSUMBLKNOMEM

RESY-5-BADBLKARRNOMEM

RESY-5-FREELSTNOMEM

RESY-5-INVCRDSTATE

RESY-5-VALOUTOFRNG

RESY-5-CORRUPTLNKDLIST

RESY-5-INVMSGTYPE

RESY-5-INVCOUNTERVAL

RESY-5-DELENTRYFAILED

RESY-5-INVALIDCASE

RESY-5-INFINITELOOP

RESY-5-TIMERCREATEFAIL

RESY-5-TIMERSTARTFAIL

RESY-5-TIMERDELFAIL

RESY-5-MALLOCFAIL

RESY-5-RELDSLVCHKSMFAI

RESY-5-INITSLVCHKSMFAI

RESY-5-INVALIDSLAVEID

RESY-5-UNKNOWNSTATE

RESY-5-INVALIDEVENT

RESY-5-RCNOTOK

RESY-5-INVALIDCODEEXEC

RESY-5-PEPEXIST

RESY-5-PEPNOTEXIST

RESY-5-GETCMTBUFFAIL

RESY-5-GETINITCKSMBUFF

RESY-5-GETADJCKSMBUFFA

RESY-5-NOTINCMTLIST

RESY-5-ALREADYFREE

RESY-5-WRONGSEQNUM

RESY-5-LEAFNULLPTR

RESY-5-ROOTNULLPTR

RESY-5-ADDCMTLISTFAIL

RESY-5-BADVSIMMSG

RESY-5-MAXCHKSMBLK0

RESY-5-INVCHKSUMBLK

RESY-5-RESIZEFAIL

RESY-5-ADDSLAVEFAIL

RESY-5-ADJSLAVEFAIL

RESY-5-RESYNCELEFAIL

RESY-5-DELELEFAIL

RESY-5-BLKMISMATCH

RESY-5-INVRSPCODE

RESY-5-ENDRCMDFAIL

RESY-5-ITFGMOREFAIL

RESY-5-SECONDCMTZERO

RESY-5-RESYNC_ERR

RESY-5-SLAVEEXISTS

RESY-5-WARINFINITELOOP

RESY-5-STRANGERSP

RESY-5-LOWMEMORY

RESY-5-OUTOFRANGE

RESY-5-CNTRLVCFAIL

RESY-5-NAKRSP

RESY-5-INVITF

RESY-5-FASTCMT

RESY-5-OLISTNOTNULL

RESY-5-BADBLKNOCONN

RESY-7-RESYNC_ENDMISMA

RESY-7-RESYNCINFO

RESY-7-CTLVCNAK

RESY-7-CMTINPROG

RESY-7-PORTDN

RESY-7-PDATATRAP

RESY-7-FREEPDATA

RESY-7-SECONDCMTFAIL

DDTS "rpm"

RMM-4-SENDCTCTASK_ERR

RMM-4-SENDCTC_MSG_PRO

RMM-4-SENDCTC_MSG_ALL

RMM-4-SENDCTC_MSG_SEN

RFS-4-NO_IPC_BUFFER

RFS-4-PORT_CREATE_ERR

RFS-4-TASK_SPAWN_ERR

RFS-5-REQ_DROP

RFS-4-GENERIC

RFS-4-GEN_ERROR

RFS-5-GEN_WARNING

RFS-6-GEN_NOTICE

RFS-7-GEN_INFO

DDTS : "rpmxf-cpro"

CPRO-7-CONNCAPEXCEED

CPRO-5-NONEXISTCONN

CPRO-4-PASSTHROREGFAIL

CPRO-3-DOWNLOADFAIL

CPRO-7-SYNCRAMERR

CPRO-4-DBMINITFAIL

CPRO-4-CPROTIMERFAIL

CPRO-4-CPROMSGHDLRFAIL

CPRO-4-INVALID_CNTRLR_

CPRO-4-SYNCRAMINITFAIL

CPRO-4-ALRM_REG_FAIL

CPRO-3-MISMATCH_CONN

CPRO-7-RINGCONGESTION

CPRO-7-RINGCONGABATE

CPRO-6-UNKNOWN_MSGTYPE

CPRO-3-FLUSHFAIL

CPRO-3-AVLFAIL

CPRO-3-CONNDB_ERR

CPRO-7-CANNOT_FIND_REC

CPRO-7-CPROTASK

CPRO-7-CHKSUM_MISMATCH

CPRO-5-NONEXISTOPSTATE

CPRO-5-EMGETOPSTATEFAI

CPRO-5-NONEXISTADMSTAT

CPRO-5-EMGETADMSTATEFA

CPRO-5-GETOPSTATEFAIL

CPRO-5-GETADMSTATEFAIL

CPRO-4-ADDCHANLOOPFAIL

CPRO-7-DELCHANLOOPFAIL

CPRO-4-NULLRSPPTR

CPRO-4-IPCMSGALLOCFAIL

CPRO-7-IPCMSGSENDSYNCF

CPRO-7-RECFOUNDNOTLPBK

CPRO-7-DALDSPCONNLOOPE

CPRO-7-DSPCHANLOOPFAIL

CPRO-7-SNMP_ERROR

CPRO-4-RAMDISK_ERR

CPRO-7-HOT_STDBY

CPRO-7-GEN_INFO

CPRO-4-TRANSACTION_ERR

CPRO-4-GENERR

CPRO-4-GENERR_NUM

CPRO-4-GENERR_NUM2

CPRO-4-GENERR_STR

CPRO-2-CNTLRLIST

CPRO-4-PASSTHRUFAIL

CPRO-4-COMEPCREATEFAIL

CPRO-4-MSGHDLRATCHFAIL

CPRO-4-BULKCNFGFAIL

CPRO-7-UNKNWNMSGTYP

RESY-7-CONNSYNCHFAIL

RESY-4-GENERR

CMM_-4-GENERR

CMM_-4-GENERR_NUM

CMM_-4-GENERR_NUM2

CMM_-4-GENERR_NUM3

CMM_-4-GENERR_NUM4

DDTS : "rpmxf-ssi"

FIPC-5-WARNING

FIPC-7-INFO

FIPC-4-COMEPSEMTAKE

FIPC-5-ISRNOTCALLABLE

FIPC-5-MCASTPSLOTINVAL

FIPC-5-MCASTPORTINVAL

FIPC-4-COMEPMALLOCERR

FIPC-4-NUMCOMEPINVALID

FIPC-4-COMEPMEMAREAERR

FIPC-5-COMEPALLOCFAIL

FIPC-5-COMEPFREEFAIL

FIPC-5-COMEPIDINVALID

FIPC-5-COMEPDELETED

FIPC-5-COMEPOWNERINVAL

FIPC-5-COMEPTYPEINVAL

FIPC-4-COMEPSEMINVALID

FIPC-4-COMEPNAMEINVAL

FIPC-5-COMEPNAMESCOINV

FIPC-4-COMEPRPLYEPDINV

FIPC-5-EPHNDLRFAIL

FIPC-5-EPHNDLRATTACHED

FIPC-5-EPWAITEXTINVPRM

FIPC-5-SYNCCTXTINUSE

FIPC-4-SYNCCTXTCLNERR

FIPC-5-SYNCINVALIDRPLY

FIPC-5-SYNCNOTSYNCRPLY

FIPC-4-MSGQDELETEFAIL

FIPC-4-MSGQCREATEFAIL

FIPC-4-MSGQDEAD

FIPC-4-HIGHMSGQDEAD

FIPC-4-LOWMSGQDEAD

FIPC-4-MSGQEVENT

FIPC-4-RETXQSIGLCKFAIL

FIPC-4-RETXQSGUNLKFAIL

FIPC-5-RETXQMQCHAINERR

FIPC-5-RETXQTIMERSET

FIPC-5-RETXQTIMRCANCEL

FIPC-4-MBLKMPOOLCRTERR

FIPC-4-MBLKBPOOLCRTERR

FIPC-4-MBLKBUFDESCERR

FIPC-5-DBUFSIZEINVALID

FIPC-4-MBLKALLOCFTLERR

FIPC-4-MBLKINVALID

FIPC-4-MBLKASSIGNFAIL

FIPC-5-MBLKUNAVAILABLE

FIPC-5-MBLKENQUEUED

FIPC-4-MBLKNOHDRSPACE

FIPC-4-MBLKBUFFREEFAIL

FIPC-4-MBLKFREEFAIL

FIPC-4-BUFSZERR

FIPC-5-LINKINERROR

FIPC-5-LINKOUTERROR

FIPC-4-LINKMEMALLOCERR

FIPC-5-LINKSARREGERROR

FIPC-5-LINKPLFMSLOT2RX

FIPC-5-SMSLOTERROR

FIPC-5-CTLDUPMSGFAIL

FIPC-5-CTLALLOCMSGFAIL

FIPC-4-CTLRCVEPIDERR

FIPC-4-CTLCOMEPERR

FIPC-4-CTLSYNCTMRERR

FIPC-4-CTLRETXQERR

FIPC-4-CTLHDLRATTCHERR

FIPC-4-CTLEPWAITERR

FIPC-5-CTLINVMSGTYPE

FIPC-5-CTLINVMSGVER

FIPC-5-CTLRCVMSGERR

FIPC-5-CTLTSKCREATEERR

FIPC-5-RSLVACKERR

FIPC-5-RSLVNAMELENERR

FIPC-5-CTLOUTOFMBLKS

FIPC-5-CTLBINDSTUNKN1

FIPC-5-CTLBINDSTUNKN2

FIPC-5-CTLBINDSTUNKN3

FIPC-5-CTLBINDSTUNKN4

FIPC-5-CTLBINDSTUNKN5

FIPC-4-CTLBINDSTFAIL1

FIPC-4-CTLBINDSTFAIL2

FIPC-4-CTLBINDSTFAIL3

FIPC-4-CTLUNBINDSTFAIL

FIPC-5-CTLUNBINDSTUNKN

FIPC-4-CTLMAXBUFRPLYER

FIPC-4-CTLINVIPCVER

FIPC-4-CTLINVRMTCTLMSG

FIPC-4-NAMEMEMALLOC

FIPC-4-NAMESRCSLOTINV

FIPC-4-NAMETASKCREATE

FIPC-4-NAMECOMEPCREATE

FIPC-5-NAMEINVMSGTYPE

FIPC-4-NAMEINVMSGVER

FIPC-5-NAMEENTRYOVRRID

FIPC-4-NAMEENTRYINIT

FIPC-4-NAMEARRAYFULL

FIPC-4-NAMEMSGALLCFAIL

FIPC-5-NAMEENTRYBNDINV

FIPC-5-NAMENOENTRYOUT

FIPC-5-LCNOUTOFRANGE

FIPC-4-LCNALREADYBOUND

FIPC-5-LCNSARREGFAILED

FIPC-5-LCNSARUNREGFAIL

FIPC-5-LCNEPIDINVALID

FIPC-5-LCNOWNERINVALID

FIPC-5-LCNNOTBOUND

FIPC-5-LCNMSGSENDERROR

FIPC-5-CONNREF_INVALID

FIPC-4-CONNADD_FAIL

FIPC-4-CONNDEL_FAIL

FIPC-4-LCNBIND_FAIL

FIPC-4-LCNUNBIND_FAIL

FIPC-4-CTCSTATETRAFAIL

FIPC-4-CTCEVTREGFAIL

FIPC-4-ALLOCPRIO

FIPC-4-INVNUM

FIPC-4-INVHWIDB

FIPC-4-COMEPMGRSEMTAKE

FIPC-4-P2IPCINITFAIL

FIPC-4-P2IPCBASEINITFA

FIPC-4-P2IPCLINKINITFA

FIPC-4-UNEXPECTEDEVENT

DDTS : "rpmxf-shm"

SHMA-5-UNK_MSG_TYPE

SHMA-5-INV_VER

SHMA-5-INV_CTC_PORT


DAL-2-DAL_INIT_ERR_ST

SEVERITY: Major Alert
FORMAT: "DAL Init Err line %d errno=0x%X,0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-4-DAL_ERR

SEVERITY: Error
FORMAT: "DAL Err line %d errno=0x%X,0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-4-DAL_ERR_STR

SEVERITY: Error
FORMAT: "DAL Err line %d errno=0x%X,0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-5-DAL_WARNING

SEVERITY: Warning
FORMAT: "DAL Warning line %d errno=0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection"

DAL-5-DAL_WARNING_STR

SEVERITY: Warning
FORMAT: "DAL Warning line %d errno=0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection"

DAL-7-DAL_INFO

SEVERITY: Information
FORMAT: "DAL Info line %d errno=0x%X,0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DAL Informational Event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "pxm-diag"

PXMD-4-ERR

SEVERITY: Error
FORMAT: "Line %d , Diagnostic error : %s, 0x%x, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "EM ERROR %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the EM application. It needs to be analyzed by TAC and possibly by the development team. In normal operation, such an error should never get reported."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative "
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspapslns (for SONET cards) "

EM-7-EM_EVENT

SEVERITY: Information
FORMAT: "EM Event %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "EM Informational Event"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

EM-2-NOVRAM_READ_ERR

SEVERITY: Major Alert
FORMAT: "NOVRAM Read Error %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error indicates a failure reading the NOVRAM. This failure can be for one of the following NOVRAMs
1. Front Card NOVRAM
2. Daughter Card NOVRAM
3. 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 PXM45
1. dspcds
2. dspcd <slot>
3. dsplog
On Service Module, please capture the following information
1. dspcd
2. dsplns "

EM-2-LINE_HARDWARE_E

SEVERITY: Major Alert
FORMAT: "Line Hardware Error on line %d.%d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 module
1. dspcd
2. dsplns
3. dspalms
Please capture the system log with dsplog <slot> command on PXM45."

EM-2-DAUGHTER_CARD_M

SEVERITY: Major Alert
FORMAT: "Unknown/Missing Daughter Card on bay %d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error indicates a failure in recognizing the Daughter Card in the specified bay. This can happen due to one of the followng reasons
1. Daughter Card NOVRAM is not readable
2. Daughter Card Type specified by NOVRAM is not supported
3. 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 PXM45
1. dspcds
2. dspcd <slot>
3. dsplog
On Service Module, please capture the following information
1. dspcd
2. dsplns "

EM-2-PRTSTAT

SEVERITY: Major Alert
FORMAT: "Port State Port%d Oper State%s \n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Info

DDTS "ccma"

OAM-7-LOG

SEVERITY: Information
FORMAT: "OAM event %s %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Oam Informational Event"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

OAM-4-ERROR

SEVERITY: Error
FORMAT: "OAM error %s %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "Diagnostic error : Error %s, %d, 0x%x, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "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 Bram
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

QE48-5-QE48ERR2

SEVERITY: Warning
FORMAT: "QE48 Err Status%s reg 0x%x, %s reg 0x%x,%s reg 0x%x,%s reg 0x%x"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "ccma"

QE48-5-QE48SARERR

SEVERITY: Warning
FORMAT: "QE48SAR Error %s() line %d %X,%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "drivers"

QE-4-FAIL2REFRESH

SEVERITY: Error
FORMAT: "QE Initialization Error qeInitConfigReg; qe_no = %d Refresh failed"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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 Info

QE-4-EXPMANTISAFAIL

SEVERITY: Error
FORMAT: "QE Initialization Error qeSetAcpCellCntRam; qe_no = %d GetExpMantisa failed"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The specified QE is unable to convert Cell Loss Threshold into Exp format."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

QE-5-UNKNOWNINT

SEVERITY: Warning
FORMAT: "QE Unknown Interrupt Error EQ No %d, status1 = %d, status2 = %d, status3 = %d\n"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The specified QE got unknown interrupt signal from the system."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

QE-5-ERRINTERRUPT

SEVERITY: Warning
FORMAT: "QE Unknown Interrupt Error QE No %d, status1 = %d, status2 = %d, status3 = %d\n"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The specified QE got error interrupt signal from the system."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

QE-4-QE_ERR

SEVERITY: Error
FORMAT: "QE Err %s() line %d %X,%X,%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

QE-5-QE_ERR_STR

SEVERITY: Warning
FORMAT: "QE Err %s() line %d %X,%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Device that are not supported by QE"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "drivers"

QE12-4-QESAR_ERR

SEVERITY: Error
FORMAT: "QE1210 SAR Error line %d %X,%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. do QE register dump"

QE12-5-QESAR_WARN

SEVERITY: Warning
FORMAT: "QE1210 SAR Warning line %d %X,%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. do QE register dump"

QE12-7-QESAR_INFO

SEVERITY: Information
FORMAT: "QE1210 SAR Info line %d %X,%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A Warning condition has been detected by QE SAR module"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "shm"

RED-7-MSGQSEND

SEVERITY: Information
FORMAT: "ACRED Could not send MSG to SM "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "AC_SEND_MSG_FAILED_ERR"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RED-7-GENERAL

SEVERITY: Information
FORMAT: "ACRED General ERROR"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "AC_GEN_ERR"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RED-7-INFORM

SEVERITY: Information
FORMAT: "ACRED Informational"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "AC_INFO_ERR"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RED-7-MEMCORRT

SEVERITY: Information
FORMAT: "ACRED Memory corruption in system"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "AC_MEM_ERR"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RED-7-TIMEOUT

SEVERITY: Information
FORMAT: "ACRED State Time out"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "AC_TIME_OUT_ERR"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RED-7-WRONGMSG

SEVERITY: Information
FORMAT: "ACRED Wrong Message Received"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "AC_WRONG_MSG_ERR"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RED-7-DNLDERR

SEVERITY: Information
FORMAT: "ACRED Download BRAM Failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "AC_DWNL_BRAM_ERR"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RED-7-UPLDERR

SEVERITY: Information
FORMAT: "ACRED Upload BRAM Failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "AC_UPLD_BRAM_ERR"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

DDTS "red"

REDM-7-CR_ERR

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "pnRedman is not able update standby controller on a given connection, due to either memory low or invalid request, etc."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-P2P_ADD_FAIL

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-P2P_DEL_FAIL

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-P2MP_ADD_FAIL

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-P2MP_DROP_FAIL

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-INVALID

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "pnRedman receives some invalid value, such as message, event"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-NULL_PTR

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "a data point is NULL"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-MALLOC_ERR

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "fail to allocate memory, ipc, etc."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanInitErr

SEVERITY: Information
FORMAT: "Init Failed at %s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanStdbySnd

SEVERITY: Information
FORMAT: "Send to standby error for %s "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanIovErr

SEVERITY: Information
FORMAT: "IOV error for %s "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanIpcSndEr

SEVERITY: Information
FORMAT: "Error in Ipc Send to Redman itsef "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanMallocEr

SEVERITY: Information
FORMAT: "Memory Allocation Failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanIpcMallo

SEVERITY: Information
FORMAT: "Memory Allocation Failed for Ipc for same task"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanInValidS

SEVERITY: Information
FORMAT: "Redman is in Invalid state"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanInValidE

SEVERITY: Information
FORMAT: "Invalid Event to Redman From PROOT"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanInfo

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-pRedmanNotice

SEVERITY: Notice
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanPrintDVa

SEVERITY: Information
FORMAT: "%s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanPrintXVa

SEVERITY: Information
FORMAT: "%s %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanError

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-prErrStk_1s1d

SEVERITY: Information
FORMAT: "%s %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-prErrStk_1s2d

SEVERITY: Information
FORMAT: "%s %d, %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-prErrStk_1s3d

SEVERITY: Information
FORMAT: "%s %d, %d, %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-ErrorStk_1s4d

SEVERITY: Information
FORMAT: "%s %d, %d, %d, %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-prErr_1s1d

SEVERITY: Information
FORMAT: "%s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-prErr_1s2d

SEVERITY: Information
FORMAT: "%s %d, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture log using dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-prErr_1s3d

SEVERITY: Information
FORMAT: "%s %d, %d, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prErr_1s4d

SEVERITY: Information
FORMAT: "%s %d, %d, %d, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanInfo1

SEVERITY: Information
FORMAT: "%s, %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanRootMsg

SEVERITY: Information
FORMAT: "Message Receved from root. Redman State%s, Go Event%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanTblReadE

SEVERITY: Information
FORMAT: "Table Read Error for %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: "capture dsplog -task pnRedman, dsplog -mod REDM"

REDM-7-pRedmanSwCnfErr

SEVERITY: Information
FORMAT: "SwitchCnf Error. Space Not available."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanInvalidR

SEVERITY: Information
FORMAT: "Invalid RecordNumber Received for %s."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanMaxLimit

SEVERITY: Information
FORMAT: "Maximum Limit reached for %s."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanMap

SEVERITY: Information
FORMAT: "For record num%d, Slot%d, subSlot%d, Port%d, subPort%d "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanMapErr

SEVERITY: Information
FORMAT: "No mapping available for recNo%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanDiskRetr

SEVERITY: Information
FORMAT: "DiskRetry Array is full and there are 50 entries . So this entry will not be stored in disk."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanStdByRet

SEVERITY: Information
FORMAT: "StdByRetry Array is full and there are 50 entries. So this entry will not be sent to stdby."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanRecNo

SEVERITY: Information
FORMAT: "%s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanMaxRec

SEVERITY: Information
FORMAT: "Table Name%s, MaxNo%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanitfDsp

SEVERITY: Information
FORMAT: "%s, %d.%d.%d.%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanIfCbErr

SEVERITY: Information
FORMAT: "%s, ifCb pointer to null for given interface (ifId %d.%d.%d.%d)."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanItfMapEr

SEVERITY: Information
FORMAT: "%s, %d.%d.%d.%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanDiskErr

SEVERITY: Information
FORMAT: "Error in Writing to Disk For %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Info

REDM-7-pRedmanPepDsp

SEVERITY: Information
FORMAT: "%s, ifId %d.%d.%d.%d.%d vpi %d vci %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanPepMapEr

SEVERITY: Information
FORMAT: "%s, ifId %d.%d.%d.%d.%d vpi %d vci %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanPepMap

SEVERITY: Information
FORMAT: "For record num%d, ifId %d.%d.%d.%d.%d vpi %d vci %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_1s

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_1s

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_2s

SEVERITY: Information
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_2s

SEVERITY: Information
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_3s

SEVERITY: Information
FORMAT: "%s %s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_3s

SEVERITY: Information
FORMAT: "%s %s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_1s1d

SEVERITY: Information
FORMAT: "%s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_1s1

SEVERITY: Information
FORMAT: "%s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_1s2d

SEVERITY: Information
FORMAT: "%s %d, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_1s2

SEVERITY: Information
FORMAT: "%s %d, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_1s3d

SEVERITY: Information
FORMAT: "%s %d, %d %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_1s3

SEVERITY: Information
FORMAT: "%s %d, %d %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_2s1d

SEVERITY: Information
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_2s1

SEVERITY: Information
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_2s1d

SEVERITY: Information
FORMAT: "%s %s %d %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_2s1

SEVERITY: Information
FORMAT: "%s %s %d %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-prAuditErr_3s1d

SEVERITY: Information
FORMAT: "%s %s %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-prAuditInfo_3s1

SEVERITY: Information
FORMAT: "%s %s %s %ds"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-RmMainLoopExit

SEVERITY: Notice
FORMAT: "Internal error redMainLoop exit"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-RmProotMsgError

SEVERITY: Notice
FORMAT: "IPC error %s. Failed to process proot event"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmStandbyUpdtRe

SEVERITY: Information
FORMAT: "Standby update receving error count exceeds threshold"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-CrJTimerErr

SEVERITY: Information
FORMAT: "CallRed journaling timer initialization failed%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmProotMsgProcE

SEVERITY: Information
FORMAT: "Failed to process root endpt message%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmInternalError

SEVERITY: Information
FORMAT: "Redman Internal Error %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmMissingProotS

SEVERITY: Information
FORMAT: "Redman received switchover from RAMDB, but failed to get msg from proot"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmActiveMsgProc

SEVERITY: Information
FORMAT: "Error processing message on active redman."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmStandbyUpdtRe

SEVERITY: Information
FORMAT: "Error receiving standby redman update"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmStandbyUpdtPr

SEVERITY: Information
FORMAT: "Error processing standby redman update"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmStandbyUpdtPr

SEVERITY: Information
FORMAT: "Error processing standby redman update"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmIpcEpCreateEr

SEVERITY: Information
FORMAT: "Ipc communication EP create failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmIpcEpResolveE

SEVERITY: Information
FORMAT: "Ipc communication EP resolve failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmIpcMsgAllocEr

SEVERITY: Information
FORMAT: "Ipc message allocation failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmIpcSendMsgErr

SEVERITY: Information
FORMAT: "Ipc send message failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-CrJTimerSchErr

SEVERITY: Information
FORMAT: "Timer schedule timeout failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-CrJTimerCancelE

SEVERITY: Information
FORMAT: "Timer cancel timeout failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmInvalidEvent

SEVERITY: Information
FORMAT: "Unexpected Event received. Curr State%d, Event%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmInvalidEventI

SEVERITY: Information
FORMAT: "Unexpected Event received. event ID%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmRamSyncErr

SEVERITY: Information
FORMAT: "RamSync error op%s, errno%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmIovAddErr

SEVERITY: Information
FORMAT: "Adding element to Iov failed. errno%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-RmActiveToStand

SEVERITY: Notice
FORMAT: "Redman exit from Active mainloop. Changed to standby role"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-RmStandbyToActi

SEVERITY: Notice
FORMAT: "Redman exit from Standby mainloop. Changed to Active role"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-RmRamDbReset

SEVERITY: Notice
FORMAT: "Redman receive reset from RAMDB. Reset reason%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-RmRemoteUnReg

SEVERITY: Notice
FORMAT: "Remote Unavailable from SyncRam Event. No more Update to Peer. Trying To send Msg%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-RmCardRoleChang

SEVERITY: Notice
FORMAT: "Card role change received from SyncRam while trying to send Msg%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmFuncTrace

SEVERITY: Information
FORMAT: "Function %s() entered"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-CrJDBInitErr

SEVERITY: Information
FORMAT: "CallRed journaling database initialization failed%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-CrInvalidNewSta

SEVERITY: Information
FORMAT: "Invalid new state posted to CallRed current state%d, new state%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-CrJDBRebuildErr

SEVERITY: Information
FORMAT: "CallRed Journalling database rebuild error%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-CrJDBChkPtDelRe

SEVERITY: Information
FORMAT: "Failed to add deleted record in checkpoint JDB"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-CrNewState

SEVERITY: Notice
FORMAT: "CallRed entering new state%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-6-CrCongestionOnO

SEVERITY: Notice
FORMAT: "Redman set standby journaling congestoin%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-5-CrRebuildIfCbNo

SEVERITY: Warning
FORMAT: "Can not find IFCB during rebuild. IfId%ld"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-5-CrRebuildRootTr

SEVERITY: Warning
FORMAT: "Can not get root tree for ifId%ld\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-5-CrRebuildSvcTre

SEVERITY: Warning
FORMAT: "Can not get SVC tree for ifId%ld\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-CrRebuildCallRe

SEVERITY: Information
FORMAT: "Failed to add call journaling record during rebuild %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-print3

SEVERITY: Information
FORMAT: " %s %d/%d "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-print4

SEVERITY: Information
FORMAT: " %s %d/%d/%d "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-print5

SEVERITY: Information
FORMAT: " %s %d/%d/%d/%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-print1s5d

SEVERITY: Information
FORMAT: " %s %d,%d,%d,%d,%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanRevChgRe

SEVERITY: Information
FORMAT: "DiskTable Rev Change Register error. TableId%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanRevRegDo

SEVERITY: Information
FORMAT: "DiskTable Rev Change Register Done error. TableID%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-pRedmanMaxAccIn

SEVERITY: Information
FORMAT: "DiskTable Max Access Info Get error. TableID%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-RmRamSyncRevChg

SEVERITY: Information
FORMAT: "RamSync Rev Change Register error. TransID%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A software error occurred"
RECOMMENDED ACTION: "capture dsplog -task pnRedman, dsplog -mod REDM"
REQUIRED INFO: No Required Info

REDM-7-RmRamSyncRegDon

SEVERITY: Information
FORMAT: "RamSync Register Done error. DbID%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-DbInvalidDowngr

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-4-provItfDbRRErr

SEVERITY: Error
FORMAT: "Error in Writing to PROV_ITF Disk for lower version plug & play port - recNum/portId%d %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Information
FORMAT: "%s %d %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For information only, not an error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-provRRUpdateNum

SEVERITY: Information
FORMAT: "%s %d %d %d %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For information only"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-provRRInfo_1s2d

SEVERITY: Information
FORMAT: "%s %d %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For information only"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-provRRInfo_1s1d

SEVERITY: Information
FORMAT: "%s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For information only"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-provRRInfo_1s

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For information only"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-provLRInfo_1s

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For information only"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-7-NO_BUFFER

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "resync"

RESY-5-NOTLEAFLEG

SEVERITY: Warning
FORMAT: "0x%x is not a leaf leg"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Not a leaf leg"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-LEGNULLPTR

SEVERITY: Warning
FORMAT: "%s is null for a p2mp conn ifid=%ld vpi=%d vci=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Leg ptr is null for a p2mp conn"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-BLKZEROPEP

SEVERITY: Warning
FORMAT: "%s RESYNC_PEP should not be on Block 0"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "RESYNC_PEP should not be on block 0"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVALIDFCNCALL

SEVERITY: Warning
FORMAT: "%s This function should not have been called."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The given function should not have been called because the resync commit is complete. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-APINULLPTR

SEVERITY: Warning
FORMAT: "%s Parm %s is invalid at position %d."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

RESY-5-NULLPTR

SEVERITY: Warning
FORMAT: "%s Parm %s is invalid at position %d."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Software Error. The parameter value for the named parameter acquired in named function is NULL."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-CHKSUMBLKNOMEM

SEVERITY: Warning
FORMAT: "%s Failed to allocate memory. Size requested '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "API Software Error. An attempt to allocate a newly sized Check Sum Block Table failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-BADBLKARRNOMEM

SEVERITY: Warning
FORMAT: "%s Failed to allocate memory. Size requested '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "API Software Error. An attempt to allocate a newly sized Bad Block Array failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-FREELSTNOMEM

SEVERITY: Warning
FORMAT: "%s Failed to allocate memory for free list. Size '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "API Software Error. An attempt to allocate memory for Resync Commit List."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVCRDSTATE

SEVERITY: Warning
FORMAT: "%s The card is neither an Active or Standby. %s is '0x%x'."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "We have been asked to add a connection that does not reside in either an Active or Standby Card."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-VALOUTOFRNG

SEVERITY: Warning
FORMAT: "%s %s=%d != %s=%d at position %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "First value given is greater than resync's value. The system was not updated accordingly."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-CORRUPTLNKDLIST

SEVERITY: Warning
FORMAT: "%s %s does not contain what we are expecting at '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

RESY-5-INVMSGTYPE

SEVERITY: Warning
FORMAT: "%s Expecting %s, received '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "We are expecting a certain message type but received another."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVCOUNTERVAL

SEVERITY: Warning
FORMAT: "%s %s decremented beyond valid range, value %d. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The given counter has been decremented beyond valid range another."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-DELENTRYFAILED

SEVERITY: Warning
FORMAT: "%s Delete entry call failed, return code '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Eitehr the list is already empty or it is corrupt."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVALIDCASE

SEVERITY: Warning
FORMAT: "%s Switch on %s produced unexpected value '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we performed a switch on a given switch statement whose value was not expected."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INFINITELOOP

SEVERITY: Warning
FORMAT: "%s Infinite Loop encountered."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we traversed a loop greater than the possible maximum for the value we are looking for."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-TIMERCREATEFAIL

SEVERITY: Warning
FORMAT: "%s We failed to create a a timer."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we used SSI to create a timer which we failed at."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-TIMERSTARTFAIL

SEVERITY: Warning
FORMAT: "%s We failed to start a timer. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we used SSI to start a timer which we failed at."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-TIMERDELFAIL

SEVERITY: Warning
FORMAT: "%s We failed to delete a timer."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we used SSI to delete a timer which we failed at creating."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-MALLOCFAIL

SEVERITY: Warning
FORMAT: "%s Failed to allocate memory of size'0x%x', memType'0x%x', Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we failed to allocate memory for the given amount and memory type."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-RELDSLVCHKSMFAI

SEVERITY: Warning
FORMAT: "%s Failed to reload slave's checksum, slaveId='0x%x', RC='0x%x'."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we failed to reload check sum for the given slave."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INITSLVCHKSMFAI

SEVERITY: Warning
FORMAT: "%s Failed to init slave's checksum, RC='0x%x'."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we failed to init checksum."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVALIDSLAVEID

SEVERITY: Warning
FORMAT: "%s Slave Id encountered is invalid '0x%x'."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we encountered an invalid slave Id"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-UNKNOWNSTATE

SEVERITY: Warning
FORMAT: "%s Given state, '0x%x', is unknown."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

RESY-5-INVALIDEVENT

SEVERITY: Warning
FORMAT: "%s Given event, '0x%x', is invalid in this state '0x%x'."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we are in a state where we don't know how to handle this event. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-RCNOTOK

SEVERITY: Warning
FORMAT: "%s We called %s, but it did not return OK, rc '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we called the given function name, however it returned the given return code."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVALIDCODEEXEC

SEVERITY: Warning
FORMAT: "%s We executed a portion of code that we should not have."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

RESY-5-PEPEXIST

SEVERITY: Warning
FORMAT: "%s Pep already in resync database."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot add pep to the resync database. It already exists."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-PEPNOTEXIST

SEVERITY: Warning
FORMAT: "%s Pep not in resync database."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot delete pep from the resync database. No such pep exists."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-GETCMTBUFFAIL

SEVERITY: Warning
FORMAT: "%s vsimwGetConnCmtMsgBuf return NULL."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Fail to get buffer for connection commit message."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-GETINITCKSMBUFF

SEVERITY: Warning
FORMAT: "%s vsimwGetInitChksumInfoMsgBuf return NULL."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Fail to get buffer for init checksum message."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-GETADJCKSMBUFFA

SEVERITY: Warning
FORMAT: "%s vsimwGetAdjustChksumRequestMsgBuf return NULL."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Fail to get buffer for adjust checksum message."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-NOTINCMTLIST

SEVERITY: Warning
FORMAT: "%s Can't delete, entry not in cmt list"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot delete, entry not in commit list"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-ALREADYFREE

SEVERITY: Warning
FORMAT: "%s Can't add to free list, already freed"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot add to free list, already freed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-WRONGSEQNUM

SEVERITY: Warning
FORMAT: "%s Wrong resync seq number. seqNum=%d resyncSeqNum=%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Wrong resync sequence number"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-LEAFNULLPTR

SEVERITY: Warning
FORMAT: "%s %s is null for a scaled master conn ifid=%ld vpi=%d vci=%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Leaf ptr is null for a scaled master conn"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-ROOTNULLPTR

SEVERITY: Warning
FORMAT: "%s %s is null for a scaled slave conn ifid=%ld vpi=%d vci=%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Root ptr is null for a scaled slave conn"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-ADDCMTLISTFAIL

SEVERITY: Warning
FORMAT: "%s Can't add into commit list"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot add to commit list"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-BADVSIMMSG

SEVERITY: Warning
FORMAT: "%s Bad vsim message type"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Bad vsim message type"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-MAXCHKSMBLK0

SEVERITY: Warning
FORMAT: "%s maxChksmBlk or slaveId is 0,intf(0x%x)"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "maxChksmBlk or slaveId is 0"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVCHKSUMBLK

SEVERITY: Warning
FORMAT: "%s vsiChksmBlk >= maxChksmBlk, vsiChksmBlk = %d, maxChksmBlk %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "vsiChksmBlk >= maxChksmBlk"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-RESIZEFAIL

SEVERITY: Warning
FORMAT: "%s cannot resize checksum table"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot resize checksum table"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-ADDSLAVEFAIL

SEVERITY: Warning
FORMAT: "%s cannot add %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot add slave"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-ADJSLAVEFAIL

SEVERITY: Warning
FORMAT: "%s cannot adjust %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot adjust slave"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-RESYNCELEFAIL

SEVERITY: Warning
FORMAT: "%s cannot alloc & init resync element"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot alloc & init resync element"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-DELELEFAIL

SEVERITY: Warning
FORMAT: "%s cannot delete resync element"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Cannot delete resync element"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-BLKMISMATCH

SEVERITY: Warning
FORMAT: "%s checksum block mismatch, resync blk %d blk %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Checksum block mismatch"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVRSPCODE

SEVERITY: Warning
FORMAT: "%s Invalid response code for cmt rsp msg. rsp code=%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Invalid response code for cmt response message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-ENDRCMDFAIL

SEVERITY: Warning
FORMAT: "%s Fail to send end resync cmd, fail reason %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Fail to send end resync command"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-ITFGMOREFAIL

SEVERITY: Warning
FORMAT: "%s Fail to send interface getmore msg, fail reason %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Fail to send interface getmore msg"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-SECONDCMTZERO

SEVERITY: Warning
FORMAT: "%s second commit counter is zero"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "second commit counter is zero"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-RESYNC_ERR

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "System Error in Resync"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-SLAVEEXISTS

SEVERITY: Warning
FORMAT: "%s Tried to add slave,Id '0x%x', that already exists. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we attempted to add a salve entry in the resync slave table but it already exists."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-WARINFINITELOOP

SEVERITY: Warning
FORMAT: "%s Infinite Loop encountered, traversed '0x%x' times."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we traversed a loop greater than the given theoretical maximum. Should this be of concern. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-STRANGERSP

SEVERITY: Warning
FORMAT: "%s Response '0x%x' with reason '0x%x'."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

RESY-5-LOWMEMORY

SEVERITY: Warning
FORMAT: "%s System Memory is low. "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

RESY-5-OUTOFRANGE

SEVERITY: Warning
FORMAT: "%s %s is at %d. Its out of range. "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Resync has accessed an internal variable that is out of expected range."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-CNTRLVCFAIL

SEVERITY: Warning
FORMAT: "%s Control VC commit NACKed, VPI %d VCI %d IFid%ld. "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Resync has received NACK for Control VC commit. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-NAKRSP

SEVERITY: Warning
FORMAT: "%s NACK response received"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Nak response received"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-INVITF

SEVERITY: Warning
FORMAT: "%s Invalid %s interfaces. pri_itf %ld sec_itf %ld"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid interfaces during addPep."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-FASTCMT

SEVERITY: Warning
FORMAT: "%s Fast resync commit counter is non zero when done"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Fast resync commit counter is non zero when done."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-OLISTNOTNULL

SEVERITY: Warning
FORMAT: "%s pResyncOutstandingListHead is not null at position %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "pResyncOutstandingListHead is not null"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-5-BADBLKNOCONN

SEVERITY: Warning
FORMAT: "%s No conn in resync db for bad blk %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "No connection in resync db for bad block"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-7-RESYNC_ENDMISMA

SEVERITY: Information
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "End resync info in Resync"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-7-RESYNCINFO

SEVERITY: Information
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Resync general info"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-7-CTLVCNAK

SEVERITY: Information
FORMAT: "Ctlvc %s received. Rsn Code%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-7-CMTINPROG

SEVERITY: Information
FORMAT: "%s Master %lx/%d/%d Slave %lx/%d/%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Commit already in progress"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-7-PORTDN

SEVERITY: Information
FORMAT: "%s interface %lx or %lx is down"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Port down"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-7-PDATATRAP

SEVERITY: Information
FORMAT: "%s %s is %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Received pdata trap for non conn commit cmd msg"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-7-FREEPDATA

SEVERITY: Information
FORMAT: "%s %s is %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Received free pdata for non conn commit cmd msg"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RESY-7-SECONDCMTFAIL

SEVERITY: Information
FORMAT: "%s second commit fail for ifid=%ld vpi=%d vci=%d rsp code=%d reason code=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Second commit fail"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "rpm"

RMM-4-SENDCTCTASK_ERR

SEVERITY: Error
FORMAT: "CTC MSG send Task Error: %s."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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) dspcds
b) dspcd
c) dsperr
d) dsplog
e) dspred
f) dir "E:RPM"

RMM-4-SENDCTC_MSG_PRO

SEVERITY: Error
FORMAT: "CTC Event Message Processing Error: %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "CTC Event Message Alloc Error: %s: %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "CTC Event Message Processing Error: %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s%d Could not get IPC buffer."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "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) dspcds
b) dspcd
c) dsperr
d) dsplog
e) dspred
f) dir "ERPM"

RFS-4-PORT_CREATE_ERR

SEVERITY: Error
FORMAT: "Could not create port %s."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "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) dspcds
b) dspcd
c) dsperr
d) dsplog
e) dspred
f) dir "ERPM"

RFS-4-TASK_SPAWN_ERR

SEVERITY: Error
FORMAT: "Could not spawn task %s."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "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) dspcds
b) dspcd
c) dsperr
d) dsplog
e) dspred
f) dir "ERPM"

RFS-5-REQ_DROP

SEVERITY: Warning
FORMAT: "RFS request type %d DROPPED."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "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) dspcds
b) dspcd
c) dsperr
d) dsplog
e) dspred
f) dir "ERPM"

RFS-4-GENERIC

SEVERITY: Error
FORMAT: "%s %s %s."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "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: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error will be logged due any of the following.
1. Unable to open desired file from E;RPM
2. Unable to get the stats of specific file
3. Trying to load Invalid file which is not there in ERPM
4. Unable to removed the specific file
5. Invalid File Descriptor
6. Unable to close the file
7. Trying to remove when the file is in Use
8. Unable to remove the file from Standby PXM
9. Unable to rename the file
10. Unable to create a directory
11. Unable to remove a directory
12. Unable to read the file
13. Unable to write the file
14. Unable to seek from the file
15. File name too long when translating the device name prefix
16. Failed to register RFS server port "
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RFS-5-GEN_WARNING

SEVERITY: Warning
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For logging all RFS related warnings"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RFS-6-GEN_NOTICE

SEVERITY: Notice
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For logging all RFS related notices"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

RFS-7-GEN_INFO

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "For logging all RFS related info messages"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

DDTS : "rpmxf-cpro"

CPRO-7-CONNCAPEXCEED

SEVERITY: Information
FORMAT: "Connection capacity of card reached"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Software limit for the provisioned connection capacity has been reached. Cannot provision any more connections."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-5-NONEXISTCONN

SEVERITY: Warning
FORMAT: "Connection %d.%d.%d does not exist"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-4-PASSTHROREGFAIL

SEVERITY: Error
FORMAT: "Could not register for passthrough"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-3-DOWNLOADFAIL

SEVERITY: Minor Alert
FORMAT: "Error downloading from disk"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-7-SYNCRAMERR

SEVERITY: Information
FORMAT: "Sync Ram Error at line %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-4-DBMINITFAIL

SEVERITY: Error
FORMAT: "Error registering with DB manager"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-4-CPROTIMERFAIL

SEVERITY: Error
FORMAT: "Could not start cPro timer"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-4-CPROMSGHDLRFAIL

SEVERITY: Error
FORMAT: "Error attaching cPro msg handler; errno = %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-4-INVALID_CNTRLR_

SEVERITY: Error
FORMAT: "Error in retrieving controller information"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-4-SYNCRAMINITFAIL

SEVERITY: Error
FORMAT: "line %d: Ram Sync %s error - errno = 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-4-ALRM_REG_FAIL

SEVERITY: Error
FORMAT: "Error registering with Card alarm manager"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-3-MISMATCH_CONN

SEVERITY: Minor Alert
FORMAT: "Mismatch on connection %d.%d.%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 to
admin down and up the connection.
b) If this is a slave endpoint, then delete
and readd the whole connection. If either of them, does not help please collect the following info and inform TAC:"
REQUIRED INFO: a) dspcds on PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-7-RINGCONGESTION

SEVERITY: Information
FORMAT: "Ring Congested; Wr:%d Rd:%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Ring Congested."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-RINGCONGABATE

SEVERITY: Information
FORMAT: "Ring Congestion Abate; Wr:%d Rd:%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Ring Congestion Abate."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-6-UNKNOWN_MSGTYPE

SEVERITY: Notice
FORMAT: "Unknown message type %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Unknown message type "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-3-FLUSHFAIL

SEVERITY: Minor Alert
FORMAT: "Error flushing semaphore; errno=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-3-AVLFAIL

SEVERITY: Minor Alert
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-3-CONNDB_ERR

SEVERITY: Minor Alert
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) Coredump if the card had reset

CPRO-7-CANNOT_FIND_REC

SEVERITY: Information
FORMAT: "Could not find record for %d.%d.%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "None"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPROTASK

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid CTC transition prevented"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CHKSUM_MISMATCH

SEVERITY: Information
FORMAT: "Checksum mismatch in Record %d: disk %d record %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-5-NONEXISTOPSTATE

SEVERITY: Warning
FORMAT: "EM OpState invalid for ifNum %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-5-EMGETOPSTATEFAI

SEVERITY: Warning
FORMAT: "EM Get OpState fails for ifNum=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-5-NONEXISTADMSTAT

SEVERITY: Warning
FORMAT: "EM AdmState invalid for ifNum %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-5-EMGETADMSTATEFA

SEVERITY: Warning
FORMAT: "EM Get AdmState fails for ifNum %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-5-GETOPSTATEFAIL

SEVERITY: Warning
FORMAT: "cPro Get OpState fails for ifNum %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-5-GETADMSTATEFAIL

SEVERITY: Warning
FORMAT: "cPro Get AdmState fails for ifNum %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Action
REQUIRED INFO: No Required Info

CPRO-4-ADDCHANLOOPFAIL

SEVERITY: Error
FORMAT: "cPro Addchanloop fails. ifNum=%d, vpi=%d, vci=%d, dir=%d."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) dspconinfo on PXM
h) dsppnports on PXM
i) dsplns on AXSM
h) dspports on AXSM
h) dspspvcifs on AXSM
h) dspcon on AXSM

CPRO-7-DELCHANLOOPFAIL

SEVERITY: Information
FORMAT: "cPro Delchanloop fails. ifNum=%d, vpi=%d, vci=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) dspconinfo on PXM
h) dsppnports on PXM
i) dsplns on AXSM
h) dspports on AXSM
h) dspspvcifs on AXSM
h) dspcon on AXSM

CPRO-4-NULLRSPPTR

SEVERITY: Error
FORMAT: "Null response ptr is returned"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) dspconinfo on PXM
h) dsppnports on PXM
i) dsplns on AXSM
h) dspports on AXSM
h) dspspvcifs on AXSM
h) dspcon on AXSM

CPRO-4-IPCMSGALLOCFAIL

SEVERITY: Error
FORMAT: "IPC Message Allocation failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) dspconinfo on PXM
h) dsppnports on PXM
i) dsplns on AXSM
h) dspports on AXSM
h) dspspvcifs on AXSM
h) dspcon on AXSM
rther analysis. DE may want to investigate on live system. Pls DO NOT reset/switchover to redundant card"

CPRO-7-IPCMSGSENDSYNCF

SEVERITY: Information
FORMAT: "IPC Message SendSync failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 PXM
b) dspred on PXM
c) dspcd <slot> on PXM
d) dspcd on the affected slot
e) dsprevs on PXM
f) All event logs prior to event (dsplog)
g) All error logs prior to event (dsperr)
h) dspconinfo on PXM
h) dsppnports on PXM
i) dsplns on AXSM
h) dspports on AXSM
h) dspspvcifs on AXSM
h) dspcon on AXSM

CPRO-7-RECFOUNDNOTLPBK

SEVERITY: Information
FORMAT: "Connection not in loopback. ifNum=%d, vpi=%d, vci=%d, dir=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "User is attempting to delete loopback on a connection which is not in loopback."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-DALDSPCONNLOOPE

SEVERITY: Information
FORMAT: "dalDspConnLoop(ifNum=%d) return ERROR."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "dalDspConnLoop() return ERROR."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-DSPCHANLOOPFAIL

SEVERITY: Information
FORMAT: "cPro Dspchanloop fails. ifNum=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "cPro Dspchanloop fails."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-SNMP_ERROR

SEVERITY: Information
FORMAT: "SNMP error; id = %d; err : %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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 Info

CPRO-4-RAMDISK_ERR

SEVERITY: Error
FORMAT: "RamDisk error : %s; errno=%d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Alarm file RamDisk operation error."
RECOMMENDED ACTION: "Please collect the following info and contact TAC"
REQUIRED INFO: "From PXM45 :
1) dspdate
2) dsplog for this slot
3) dspver"

CPRO-7-HOT_STDBY

SEVERITY: Information
FORMAT: "dsphotstandby cmd : %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "error while executing dsphotstandby command."
RECOMMENDED ACTION: "This is an info message."
REQUIRED INFO: No Required Info

CPRO-7-GEN_INFO

SEVERITY: Information
FORMAT: "%s; %d, errno=%d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "general cpro health related info"
RECOMMENDED ACTION: "This is an Info"
REQUIRED INFO: No Required Info

CPRO-4-TRANSACTION_ERR

SEVERITY: Error
FORMAT: "connection Transaction err : %s; errno=%d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "error happened when getting/incrementing transaction id."
RECOMMENDED ACTION: "Please collect the following info and contact TAC"
REQUIRED INFO: "From PXM45 :
1) dspdate
2) dsplog for this slot
3) dspver
FROM SM :
1) dspcons
2) from the axsm shell cProTransactionHelp "

CPRO-4-GENERR

SEVERITY: Error
FORMAT: "%s, line %d: <%s>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-4-GENERR_NUM

SEVERITY: Error
FORMAT: "%s, line %d: <%s>, info = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-4-GENERR_NUM2

SEVERITY: Error
FORMAT: "%s, line %d: <%s>, info = %d %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-4-GENERR_STR

SEVERITY: Error
FORMAT: "%s, line %d: <%s>, info = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-2-CNTLRLIST

SEVERITY: Major Alert
FORMAT: "%s, line %d: <%s>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-4-PASSTHRUFAIL

SEVERITY: Error
FORMAT: "%s, line %d: Passthru Reg failed for the controller = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-4-COMEPCREATEFAIL

SEVERITY: Error
FORMAT: "%s, line %d: Endpoints creation failed cProEpId=%x iLmiEpId=%x cProCtcEpId=%x cProCdRoleEpId=%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-4-MSGHDLRATCHFAIL

SEVERITY: Error
FORMAT: "%s, line %d: Message handler attach failed for %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-4-BULKCNFGFAIL

SEVERITY: Error
FORMAT: "%s, line %d: Failure sending rsprtn info to vsis for partn = %d, returned error = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CPRO-7-UNKNWNMSGTYP

SEVERITY: Information
FORMAT: "%s, line %d: Unknown message type = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "An unknown message type has been received and dumped"
RECOMMENDED ACTION: "This is an info"
REQUIRED INFO: No Required Info

RESY-7-CONNSYNCHFAIL

SEVERITY: Information
FORMAT: "%s, line %d: Err in conn synch with vsim: error = 0x%x, vpi = %d, vci = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

RESY-4-GENERR

SEVERITY: Error
FORMAT: "%s, line %d: <%s>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CMM_-4-GENERR

SEVERITY: Error
FORMAT: "%s, line %d: <%s>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CMM_-4-GENERR_NUM

SEVERITY: Error
FORMAT: "%s, line %d: <%s>, info = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CMM_-4-GENERR_NUM2

SEVERITY: Error
FORMAT: "%s, line %d: <%s>, info = %d %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CMM_-4-GENERR_NUM3

SEVERITY: Error
FORMAT: "%s, line %d: <%s>, vpi.vci = %d.%d, error = 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

CMM_-4-GENERR_NUM4

SEVERITY: Error
FORMAT: "%s, line %d: <%s>, vpi.vci = %d.%d, error = 0x%x err str = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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/dspcd
2) dspver
3) 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 required

DDTS : "rpmxf-ssi"

FIPC-5-WARNING

SEVERITY: Warning
FORMAT: "Where: %s()::%d, Errno: 0x%x, ErrMsg: %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "FIPC warning: func()::line, Errno, Error Msg"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-7-INFO

SEVERITY: Information
FORMAT: "Where: %s()::%d, Errno: 0x%x, ErrMsg: %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "FIPC info: func()::line, Errno, Error Msg"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-COMEPSEMTAKE

SEVERITY: Error
FORMAT: "%s, line %d, Error %x taking FIPC semaphore %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, Attempt to take FIPC semaphore %x from interrupt routine"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Attempt to take FIPC semaphore from an interrupt routine"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-MCASTPSLOTINVAL

SEVERITY: Warning
FORMAT: "%s:Invalid Physical Slot number %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Physical slot number is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-MCASTPORTINVAL

SEVERITY: Warning
FORMAT: "%s:Multicast not support on port %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast is not supported for this port"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-COMEPMALLOCERR

SEVERITY: Error
FORMAT: "%s, line %d, Failed to alloc mem for CommEp array (lstSize %d, arraySize %d)"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Desired number of Comm Eps %d exceeds the system limit %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Insufficient memory for Comm Ep array: Want %d, %d; Got %d, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, Failed to allocate an FIPC Comm. endpoint at %p"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed to allocate an FIPC communications Endpoint"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-COMEPFREEFAIL

SEVERITY: Warning
FORMAT: "%s, line %d, Failed to free an FIPC Comm Endpoint %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed to free an FIPC communications Endpoint"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-COMEPIDINVALID

SEVERITY: Warning
FORMAT: "%s, line %d, An invalid FIPC_COM_EPID of %p was passed as an argument."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, Non-existing CommEp %p has invalid tag %p; Expected tag is %p."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A non-existing communications Endpoint"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-COMEPOWNERINVAL

SEVERITY: Warning
FORMAT: "%s, line %d, Communication Endpoint %x: access by non-owner task"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Communication Endpoint being accessed by non-owner task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-COMEPTYPEINVAL

SEVERITY: Warning
FORMAT: "%s, line %d, Communication Endpoint %x: invalid type %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Communication Endpoint not IPC plain Async EndPoint"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-COMEPSEMINVALID

SEVERITY: Error
FORMAT: "%s, line %d, Invalid semaphore %p in Comm Ep %p"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Communication Endpoint's %x global name %s too long"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, Name Scope %d is invalid"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Communication Endpoint NameScope invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-COMEPRPLYEPDINV

SEVERITY: Error
FORMAT: "%s, line %d, Couldn't get task's Sync Rply Epid, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, FIPC EPHandler %x on Ep %x returning errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "FIPC Endpoint handler returned error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-EPHNDLRATTACHED

SEVERITY: Warning
FORMAT: "%s, line %d, Com Ep %x already has EP Handler attached"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Communication Endpoint is already attached"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-EPWAITEXTINVPRM

SEVERITY: Warning
FORMAT: "%s, line %d, Status parameter %x to ssiIpcComEpWaitExit is invalid"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "ssiIpcComEpWaitExit received an invalid status parameter"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-SYNCCTXTINUSE

SEVERITY: Warning
FORMAT: "%s, line %d, Sync context in use in Comm Epid %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Sync Context is already in use for this EPID"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-SYNCCTXTCLNERR

SEVERITY: Error
FORMAT: "%s, line %d, Failed to cleanup sync context for epid %x, errno %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, Invalid sync reply on epid %s, Epid %x (%x), SeqNum %d (%d)"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid sync reply on an Endpoint"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-SYNCNOTSYNCRPLY

SEVERITY: Warning
FORMAT: "%s, line %d, Received msg not Sync Reply on epid %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Received message is not a Sync reply on the endpoint"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-MSGQDELETEFAIL

SEVERITY: Error
FORMAT: "%s, line %d, Failed to delete FIPC message queue, queue %x, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Failed to create FIPC message queue, error %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, FIPC message queue, queue %x is dead"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, FIPC message High queue, queue %x is dead"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, FIPC message Low queue, queue %x is dead"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, FIPC MsgQ Event: %s, queue %x, parameters %x, %x, %x, %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Message Queue Event Occurred"
RECOMMENDED ACTION: "No action required. This is just an event occurred in the msg Queue"
REQUIRED INFO: No Required Info

FIPC-4-RETXQSIGLCKFAIL

SEVERITY: Error
FORMAT: "%s, line %d, Failed to lock timer signal, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Failed to unlock timer signal, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, %s, Retxq %x Got %x, Expected %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Message not the first msg in the chain"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-RETXQTIMERSET

SEVERITY: Warning
FORMAT: "%s, line %d, RetxQ %x: timer set error %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Retransmission queue time set error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-RETXQTIMRCANCEL

SEVERITY: Warning
FORMAT: "%s, line %d, RetxQ %x: timer cancel error %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Retransmission queue timer cancel error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-MBLKMPOOLCRTERR

SEVERITY: Error
FORMAT: "%s, line %d, Failed to create FIPC mblk pool (tot. mblks %d, fltg. mblks %d)"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Failed to create FIPC buffer pool(buf size %d, num bufs %d)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Failed to alloc FIPC buffer descriptor memory (num buf desc %d)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, Requested data buffer size %d exceeds system max buffer size"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Requested data buffer size exceeds the system max buf size"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-MBLKALLOCFTLERR

SEVERITY: Error
FORMAT: "%s, line %d, Fatal error %x allocating floating mblk, mblk control corrupted "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Invalid message descriptor"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Message assignment failed: %s %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, No mblk available for a buffer - mblk pool corrupted"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "No mblk available for a buffer - mblk pool corrupted"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-MBLKENQUEUED

SEVERITY: Warning
FORMAT: "%s, line %d, Epid %x; Msg %x already enqueued, next %x, datap %x, owner %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Memory block is already enqueued and in use"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-MBLKNOHDRSPACE

SEVERITY: Error
FORMAT: "%s, line %d, No space for header, errno %x, Wanted %d, Got %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Failed to free data buffer %x, errno %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Failed to free mblk %x, errno %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Failed to get padding size for chunk data size %d, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, FIPC Link rcv error %x, link %x; Expected %x, Got %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "FIPC link receive error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-LINKOUTERROR

SEVERITY: Warning
FORMAT: "%s, line %d, FIPC Link snd error %x; Expected %x, Got %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "FIPC link send error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-LINKMEMALLOCERR

SEVERITY: Error
FORMAT: "%s, line %d, Failed to allocate memory for link cfg table (num links %d)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, %d: Error %x registering link %d (slot %d) lcn=0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error encountered in registering link"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-LINKPLFMSLOT2RX

SEVERITY: Warning
FORMAT: "%s, line %d, Platform cannot translate RxLcn for slot %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Platform cannot translate the receive LCN"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-SMSLOTERROR

SEVERITY: Warning
FORMAT: "%s, line %d, Error %x and SM slot no passed is %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error encountered for the specified SM slot"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-CTLDUPMSGFAIL

SEVERITY: Warning
FORMAT: "%s, line %d, Error %x duplicating message"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error encountered in duplicating the message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-CTLALLOCMSGFAIL

SEVERITY: Warning
FORMAT: "%s, line %d, Error %x allocating message"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error encountered in allocating the message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-4-CTLRCVEPIDERR

SEVERITY: Error
FORMAT: "%s, line %d, Error getting caller task's Receive Sync Epid"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Error %x instantiating FIPC Control Port"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Error %x initializing FIPC Sync Timer"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Error %x initializing FIPC Retransmission Queue"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Error %x attaching EP Wait handler to IPC Ctl queue"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Error
FORMAT: "%s, line %d, Error %x exiting from EP Wait handler"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "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: Warning
FORMAT: "%s, line %d, Invalid FIPC Ctl msg type %x, arg %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid FIPC control message type"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FIPC-5-CTLINVMSGVER

SEVERITY: Warning