Table Of Contents

SHMA-5-INV_SYNC_MSG

SHMA-5-INV_MSG_PTR

SHMA-4-MISSING_IE

SHMA-5-RMI_SEND_ERR

SHMA-5-SEND_ERR

SHMA-5-API_ACT_CTL_ERR

SHMA-5-API_MALLOC_ERR

SHMA-5-FRAME_ALLOC_ERR

SHMA-4-EXTEND_TMR_ERR

SHMA-7-EXTEND_TMR_OK

SHMA-7-INV_EXTPOLL_RES

SHMA-4-RMI_INV_PARAM

SHMA-4-EPIDX_INIT_ERR

SHMA-4-RMI_RETXQ_ERR

SHMA-4-RMI_IPC_ERR

SHMA-4-INV_EPIDX

SHMA-4-INV_MBPTR

SHMA-5-RMI_INV_EPIDX

SHMA-5-RMI_INV_RCV_ID

SHMA-5-RETX_ACK_ERR

SHMA-5-RETX_NACK_ERR

SHMA-4-RMI_INV_MSG_PTR

SHMA-4-API_MSG_HDR_ERR

SHMA-4-MSG_IPC_SND_ERR

SHMA-4-NOT_OWNER_ERR

SHMA-4-PORT_NOT_INIT

SHMA-5-PORT_INIT_WARN

SHMA-4-PORT_INIT_ERR

SHMA-4-RMT_CTXT_ERR

SHMA-4-RETX_Q_ERR

SHMA-4-MSG_FREE_ERR

SHMA-5-MSG_DUP_ERR

SHMA-5-MSG_MALLOC_ERR

SHMA-5-INV_MSG_PARAM

SHMA-5-INV_MSG_TYPE

SHMA-7-API_RS_REPORT

SHMA-7-FATAL_ERR_RPT

SHMA-7-FRUMISMATCH_RPT

SHMA-7-RESCDTYPE_SET_R

SHMA-7-INVALID_PARAMS

DDTS : "rpmxf-traps"

TRAP-4-TRAPCL_COMEP

TRAP-5-TRAPCL_BINDEP

TRAP-4-TRAPCL_TIMER_CR

TRAP-4-TRAPCL_ATTHDLR

TRAP-4-TRAPCL_INTQ_FRE

TRAP-5-TRAPCL_INTQ_ALL

TRAP-5-TRAPCL_INTQ_GET

TRAP-4-TRAPCL_FREE

TRAP-5-TRAPCL_BAD_MSGF

TRAP-5-TRAPCL_TMR_SCHD

TRAP-5-TRAPCL_TMR_CNCL

TRAP-5-TRAPCL_INV_SEQN

TRAP-5-TRAPCL_FLUSHEP

TRAP-5-TRAPCL_BADEP

TRAP-5-TRAPCL_INVSLOT

TRAP-5-TRAPCL_SENDERR

TRAP-5-TRAPCL_DUPERR

TRAP-4-TRAPCL_ASSIGNEP

TRAP-7-TRAPCL_DROPPED

TRAP-4-TRAPCL_NAMESIZE

TAPI-4-INVALIDINPUT

TAPI-5-PARMOUTOFTRANGE

TAPI-4-PARMINVALID

TAPI-4-PARMINVLENGTH

TAPI-4-FUNCFAIL_STKDUM

TAPI-5-INVALIDNUM

TAPI-5-QUEUEFULL

TAPI-5-INVOIDPTR

TAPI-5-INVPTR

TAPI-5-INVLENGTH

TAPI-5-DATAPTRGET_ERR

TAPI-7-TRAPLET_ERR

TAPI-7-IPC_ERR

DDTS : "rpmxf-sw"

VSIC-5-VSICGENERR

VSIC-2-VSIMAJORERR

VSIS-5-VSISERR

VSIS-5-GENERR

VSIS-5-GENERR_NUM

VSIS-5-GENERR_STR

VSIS-5-INITERR

VSIS-5-TASKSTATE

VSIS-5-CTCLOGPLFM

VSIS-5-CTCLOGCD

VSIS-5-CTCLOGCNTRL

VSI_-5-VSIRMERR

VSI_-5-GENERR

VSI_-5-GENERR_NUM

VSI_-5-GENERR_NUM2

VSI_-5-GENERR_STR

DDTS : "rpmxf-ctc"

ZTC-4-EMPTYMSG

ZTC-4-MEMALLOCERROR

ZTC-4-MEMFREEFAIL

ZTC-4-MSGRPLYERROR

ZTC-4-EPINSTFAIL

ZTC-4-HDLRATTACHERR

ZTC-4-PROCERROREXIT

ZTC-4-GENERR

ZTC-4-UNKNOWNMSG

DDTS : "rpmxf-alarms"

ZAM-4-EPRESOLVEFAIL

ZAM-4-EPBINDFAIL

ZAM-4-NOMEM

ZAM-4-MALLOCFAIL

ZAM-4-MEMFREEFAIL

ZAM-4-GENERR

ZAM-4-COMEPCREATEFAIL

ZAM-4-MSGHDLRATACHFAI

ZAM-4-TIMERCREATEFAIL

ZAM-4-SSITIMERFAIL

ZAM-4-SCHEDTIMEOUTFAI

ZAM-4-BADTIMERKEY

ZAM-4-SSIMESSAGEFAIL

ZAM-4-CANTREACHNAM

ZAM-4-NOALARMSUMMARY

ZAM-4-BADSEVERITY

ZAM-4-BADSTATPARAM

ZAM-4-NOSUCHALARM

ZAM-4-BADALARMLEVEL

DDTS "rpm"

RMM-5-NO_IPC_BUFFER

RMM-4-PORT_CREATE_ERR

RMM-4-SEAT_CREATE_ERR

RMM-4-SEAT_DELETE_ERR

RMM-4-TASK_SPAWN_ERR

RMM-5-UNKNOWN_MSG

RMM-5-INIT_ACK_ERR

RMM-4-TASK_INIT_ERR

RMM-4-CRDACT_WAIT_ERR

RMM-4-UNREACHABLE

RMM-7-RESYNC_SUCCESS

RMM-4-SEAT_RESYNC_ERR

RMM-4-SEAT_NOT_UP

RMM-4-INIT_FAILURE

RMM-5-BAD_NUM_VALUE

RMM-5-BAD_STR_VALUE

RMM-5-IPC_SEND

RMM-5-NO_SSI_BUF

RMM-4-NULL_PTR

RMM-4-GEN_ERR

RMM-4-MSG_SEND_ERR

RMM-7-CLRALLCNF

RMM-4-CLRALLCNF_ERR

RMM-4-GEN_ERROR

RMM-5-GEN_WARNING

RMM-6-GEN_NOTICE

RMM-7-GEN_INFO

RMM-4-CSR_MSG_PROC_ER

RMM-4-CSR_IPC_COMEP_C

RMM-4-CSR_IPC_HDLR_ER

RMM-4-STBY_SYNC_ERR

RMM-4-TMPCOPY_ERR

RMM-4-FILE_STAT_ERR

RMM-4-FILE_DELETE_ERR

RMM-4-CTC_EVT_TX_FAIL

RMM-5-CTC_PORT_OPEN_F

RMM-7-SWITCHOVER_NOTI

RMM-4-MAX_RETRY_SWITC

DDTS "pxm-connmgm"

RCMP-4-INIT_ERR

RCMP-7-GEN_ERR

RCMP-7-ADD_CON_ERR

RCMP-7-SRAM_ERR

DDTS "rpm"

RVT-4-INIT_ERROR

RVT-4-INIT_SYNCH_TIME

RVT-4-INIT_CONN_ALARM

RVT-7-SWAMPING

RVT-4-SWAMPING_ERROR

RVT-4-IOS_ERROR

RVT-4-BULK_SUBIF_ERR

RVT-4-CONN_RESYNC_ERR

RVT-4-SNMP_ERROR

RVT-4-SNMP_CONN_ERR

RVT-4-INIT_FEATURE_CO

RVT-7-CONFIG_COPY_EVE

RVT-5-CONFIG_COPY_FOR

RVT-5-CONFIG_COPY_FOR

RVT-4-CONFIG_COPY_WRI

RVT-4-SUBIF_SYNC_RAM_

DDTS "drivers"

SABR-2-SA_INIT_ERR

SABR-2-SA_INIT_ERR_STR

SABR-4-SA_HW_ERR

SABR-4-SA_HW_ERR_STR

SABR-5-SA_WARN

SABR-5-SA_WARN_STR

SABR-7-SA_INFO

SABR-7-SA_HMM_INFO

SAR-5-SARQUEUE

SAR-1-SAR_FRMFIFO_ERR

SAR-7-PATH_INFO

DDTS "sapi"

SAPI-4-INITERROR

SAPI-4-NOMORESESSIONS

SAPI-4-NULLHANDLERTABL

SAPI-4-INVALIDHANDLE

SAPI-4-INVALIDREQUESTT

SAPI-4-NOMESSAGEDATA

SAPI-4-NULLHEADERPARAM

SAPI-4-INVHDRPARAMS

SAPI-4-INVHDRPARAMS_SE

SAPI-4-NOREQUESTDATA

SAPI-4-COULDNOTSENDMSG

SAPI-4-COULDNOTFREEMEM

SAPI-4-COULDNOTGETSRVR

SAPI-4-QINITERROR

SAPI-4-IPCERROR

DDTS "drivers"

SAR-5-SAR_DMA_ERR

SAR-4-SAR_XMT_ERR

SAR-1-SAR_DMA_DEAD

SAR-1-SAR_DMAFRZN_ERR

SAR-1-SAR_QEINJFRZN_E

SAR-1-SAR_QEEXTFRZN_E

SAR-1-SAROVERFLOW

SAR-5-SAROVERFLOW

SAR-5-INV_SCHEDULER_F

SAR-5-SAR_RESET_QE

DDTS "drivers"

SAR2-4-INVMAGIC

SAR2-5-HDRADDERROR

SAR2-5-MAXLCNERROR

SAR2-5-FRMMAXLENERROR

SAR2-5-CELLMAXLENERROR

SAR2-5-P1SARDISPERROR

SAR2-5-P1SARSNDERROR

SAR2-5-P2INITERROR

SAR2-5-REGERROR

SAR2-5-SPIERROR

DDTS "shm"

SCM-7-MSGQRCV

SCM-4-SPI_ERROR

SCM-4-INIT

SCM-5-UNKNOWN_MSG

SCM-4-SEND_FAIL

SCM-4-HTBT_ERROR

SCM-4-OVERSIZE_FRAME

SCM-5-UNKNOWN_VALUE

SCM-5-UNKNOWN_FRAME

SCM-5-WRONG_STATE

SCM-4-NULLPTR

SCM-5-SCM_Q_OVERFLOW

SCM-5-SCM_PRI_ERROR

SCM-4-NODEST

SCM-4-SEQ_NUM_MISMTCH

SCM-4-OUT_OF_BUF

SCM-4-SAR_RCV

SCM-4-SSI_XMT

SCM-4-RESP_TIMEOUT

SCM-5-BAD_SCM_CD_ST

SCM-4-WAITING_FOR_DAC

SCM-6-CARD_INSERTION

SCM-6-RPM_IPC_FAILURE

SCM-6-RPM_IPC_RECOVER

SCM-6-RPM_NOT_RESPOND

SCM-6-RPM_RESPONDING

SCM-4-INVALID_STATE

SCM-4-HTBT_TYPE_BAD

SCM-7-PATHCHECK_REPOR

SCM-7-PATHCHECK_INFO

DDTS "sctfm"

SCTF-7-SYNCRAMERR

SCTF-7-COMEPCREATEFAIL

SCTF-7-COMEPBIND_FAIL

SCTF-7-ILLEGAL_TRANSTI

SCTF-7-CNTRLMSGHDLRFAI

SCTF-7-CLIENTMSGHDLRFA

SCTF-4-DBMINITFAIL

SCTF-6-UNKNOWN_MSGTYPE

SCTF-6-CTC_EXCEPTION

SCTF-7-SNMP_ERROR

SCTF-4-FAILED_DBCREATE

SCTF-4-FAILED_TBLCREAT

SCTF-4-FAILED_TBLNCHAN

SCTF-4-FAILED_DBREGIST

SCTF-4-FAILED_DBWRITE

SCTF-4-FAILED_MALLOC

SCTF-4-FILE_MISSING

SCTF-4-DIRECTORY_CREAT

SCTF-4-FAILED_IPCMSG_A

SCTF-4-FAILED_IPCSEND

SCTF-4-EVENT_INVALID

SCTF-4-FAILED_FUNCTION

SCTF-4-IPCDATAPTR_INVA

SCTF-7-INFO_LOG1

SCTF-7-INFO_LOG2

SCTF-7-INFO_LOG3

SCTF-7-UNKNOW_FILE

DDTS "control-point"

SLFT-4-SLFTST_FAILED

DDTS "shm"

SHM_-2-UNRES_CD_INSERT

SHM_-2-UNRES_CD_REMOVE

SHM_-7-SM_FC_RESERVED

SHM_-7-NATIVE_CHK_ABRT

SHM_-4-HMASTER_NO_HREA

SHM_-4-HW_FAILURE

SHM_-4-CD_NATIVE_ERR1

SHM_-4-CD_NATIVE_ERR2

SHM_-4-CD_NATIVE_ERR3

SHM_-4-CD_NATIVE_ERR4

SHM_-4-CD_NATIVE_ERR5

SHM_-4-CD_NATIVE_ERR6

SHM_-4-CD_NOT_HEALTHY

SHM_-2-CD_INSERT

SHM_-2-PXM_CBC_RDY

SHM_-2-PXM_CBC_NOT_RDY

SHM_-2-PXM_FW_RDY

SHM_-2-PXM_FW_NOT_RDY

SHM_-7-UNRES_CD_INSERT

SHM_-7-INSERT_CD_TYPE

SHM_-7-SET_CD_TYPE

SHM_-7-CD_FW_RDY

SHM_-7-CD_FW_NRDY

SHM_-2-CD_REMOVE

SHM_-7-UNRES_CD_REMOVE

SHM_-7-CD_READY

SHM_-7-DISK_REMOVE

SHM_-4-DISK_NOT_SYNCED

SHM_-7-DSK_ALRDY_SYNC

SHM_-7-FEATURE_MIS_CLR

SHM_-7-FEATURE_MIS_SET

SHM_-7-EXTPOLL_RESP

SHM_-7-IMG_DNLD_START

SHM_-7-IMG_DNLD_END

SHM_-4-INV_CDTYPE

SHM_-4-FILE_NOT_FOUND

SHM_-4-CD_NO_RESP

SHM_-4-MALLOC_FAIL1

SHM_-4-INV_IMG_DESC

SHM_-4-INV_IMG_FILE

SHM_-4-FILE_POS_ERR

SHM_-4-FILE_READ_ERR

SHM_-4-FILE_STAT_ERR

SHM_-7-DSK_C_RBLD_OK

SHM_-7-DSK_C_RBLD_ERR

SHM_-7-BRAM_C_RBLD_OK

SHM_-7-BRAM_C_RBLD_ERR

SHM_-7-CLRALLCNF_OK

SHM_-7-CLRALLCNF_ERR

SHM_-7-CLRCNF_OK

SHM_-7-CLRCNF_ERR

SHM_-7-RAM_INIT_OK

SHM_-7-RAM_INIT_ERR

SHM_-7-CTRL_CD_RBLD

SHM_-5-INV_SLOT

SHM_-7-INV_EXTPOLL_VER

SHM_-5-INV_API_CALL

SHM_-5-OFFLINE_DIAGREQ

SHM_-7-CD_RESET

SHM_-4-SET_CSM_TMR_ERR

SHM_-5-INV_RST_REASON

SHM_-7-CD_SWFWVERS_CLE

SHM_-7-BC_INFO_CORRECT

SHM_-7-CD_NVIDS_CLEARE

SHM_-5-DB_CORRUPTION

SHM_-2-FAT_SPAWN_TASK

SHM_-1-CD_ST_CHG

SHM_-7-NODE_RESET

SHM_-1-ACT_CTLR_CD_RST

SHM_-6-STB_CTLR_CD_RST

SHM_-7-NODE_RESET2

SHM_-7-CARD_RESET

SHM_-7-CD_RESET_SKIP

SHM_-1-CD_RST_FAIL

SHM_-4-NOVRAM_FAIL

SHM_-4-BRAM_CHKSUM_ERR

SHM_-4-CLR_BRAM_ERR

SHM_-4-READ_BRAM_ERR

SHM_-2-BRAM_WRITE_FAIL

SHM_-4-DSK_DIR_DEL_ERR

SHM_-4-DSK_CHKSUM_ERR

SHM_-4-READ_DISK_ERR

SHM_-1-FAT_CD_DEAD

SHM_-2-EXT_POLL_FAIL

SHM_-4-UNEXP_NULL_PTR

SHM_-5-MALLOC_FAIL2

SHM_-4-BAD_DSK_SLOT_ST

SHMA-5-INV_SYNC_MSG

SEVERITY: Warning

FORMAT: "%s:Unexpected IPC sync message arrived at CTC port"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Sync messages are not expected to arrive at the CTC port, only SCCP messages"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-INV_MSG_PTR

SEVERITY: Warning

FORMAT: "%s: Invalid message pointer passed to the CTC RMI handler"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "There is probably an internal error in RMI"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-4-MISSING_IE

SEVERITY: Error

FORMAT: "%s: %s Message, Missing IE mask 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "A message from shelf manager is rejected due to missing information elements"

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.

SHMA-5-RMI_SEND_ERR

SEVERITY: Warning

FORMAT: "%s: RMI Msg Send fail epidx 0x%x, dstEpid %d, port 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to send a message through RMI. The failure reason can be an unknown destination epid, wrong local RMI epidx or invalid RMI port"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-SEND_ERR

SEVERITY: Warning

FORMAT: "%s: Failed to send a message to queue 0x%x, errno 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to send a message to a message queue. The failure reason could be an unknown message queue"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-API_ACT_CTL_ERR

SEVERITY: Warning

FORMAT: "%s: Active controller phys lot id unknown, errno 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The card does not know the physical slot id of the active shelf controller"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-API_MALLOC_ERR

SEVERITY: Warning

FORMAT: "%s: Failed to allocate an RMI message, errno 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "IPC Message pool must be seriously depleted"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-FRAME_ALLOC_ERR

SEVERITY: Warning

FORMAT: "%s: Failed to allocate an SSI Frame Buffer, errno 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SSI Frame Buffer Pool must have been seriously depleted"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-4-EXTEND_TMR_ERR

SEVERITY: Error

FORMAT: "%s line %d: failed to extend timer, returnCode %d, errno 0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "CTC failed to request for more time from SHM"

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

REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Technical support representative.

SHMA-7-EXTEND_TMR_OK

SEVERITY: Information

FORMAT: "%s line %d: pslot %d, timer extended by %d seconds, state %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "CTC gets OK for requesting more time from SHM"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-7-INV_EXTPOLL_RES

SEVERITY: Information

FORMAT: " %s : Invalid Ext. Poll Response from slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Received an invalid Extended Poll response"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-4-RMI_INV_PARAM

SEVERITY: Error

FORMAT: " %s line %d: Invalid parameter %s 0x%x (%d)"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invalid EPID from User"

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

REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Technical support representative.

SHMA-4-EPIDX_INIT_ERR

SEVERITY: Error

FORMAT: " %s, line %d, Epidx Init Error %s: Got 0x%x expected %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error during the creation of an EPIDX"

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

REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Technical support representative.

SHMA-4-RMI_RETXQ_ERR

SEVERITY: Error

FORMAT: "%d: error in retransmission Q operation %s line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error in retransmission queue function"

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.

SHMA-4-RMI_IPC_ERR

SEVERITY: Error

FORMAT: "%d: error in IPC operation %s line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error in IPC Function"

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.

SHMA-4-INV_EPIDX

SEVERITY: Error

FORMAT: "%s invalid EpidIdx %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invalid EPID Index from User"

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.

SHMA-4-INV_MBPTR

SEVERITY: Error

FORMAT: "%s %d invalid Mbptr 0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: " App passed invalid mbPtr is NULL. The Mbptr was got without shmSmcMsgAllocate()"

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.

SHMA-5-RMI_INV_EPIDX

SEVERITY: Warning

FORMAT: "%s line %d: Invalid Epidx %d, endPointPtr 0x%x, index %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An unexpected sync IPC message arrived. It could not be handled"

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.

SHMA-5-RMI_INV_RCV_ID

SEVERITY: Warning

FORMAT: "%s line %d: Invalid RcvId (0x%x-0x%x-%d) on Epid 0x%x Port %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An unexpected sync IPC message arrived. It could not be handled"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-RETX_ACK_ERR

SEVERITY: Warning

FORMAT: "%s, line %d, Error %s: Epid 0x%x Port %d, handle %4x-%4x,lastAckdSeqNum %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error trying to get the original message from the retransmission queue using Ack. The original message may never have been put on the queue or the message handle was not re-created properly."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-RETX_NACK_ERR

SEVERITY: Warning

FORMAT: "%s, line %d, Error %s: Epid 0x%x Port %d, handle %4x-%4x,lastAckdSeqNum %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error trying to get the original message from the retransmission queue using NACK. The original message may never have been put on the queue or the message handle was not recreated properly."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-4-RMI_INV_MSG_PTR

SEVERITY: Error

FORMAT: "%s, line %d, Invalid Msg Ptr, msgType %d, Epid 0x%x, Port %d, SeqNum %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invalid message pointer was passed into the function. This is an internal software 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.

SHMA-4-API_MSG_HDR_ERR

SEVERITY: Error

FORMAT: "%s, line %d, No space for MsgHdr, msgType %d, Epid 0x%x, Port %d, SeqNum %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "There is not enough space on the message to put the MC message header on the message. This is an internal software error. The caller probably did not use shmMscMsgAllocate() to get the message"

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.

SHMA-4-MSG_IPC_SND_ERR

SEVERITY: Error

FORMAT: "%s, line %d, Error 0x%x sending msgType %d, Epid 0x%x, Port %d, SeqNum %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "The specified IPC error occurred while sending the specified message"

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.

SHMA-4-NOT_OWNER_ERR

SEVERITY: Error

FORMAT: "%s, line %d: Non-owner task 0x%x attempting to use Epidx %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "A non-owner task is trying to operate on the specified Epidx. This is an internal software 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.

SHMA-4-PORT_NOT_INIT

SEVERITY: Error

FORMAT: "%s, line %d: Port %d not initialized on Epidx %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Attempted operation on an RMI port that is not initialized"

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.

SHMA-5-PORT_INIT_WARN

SEVERITY: Warning

FORMAT: "%s, line %d: Port %d not initialized on Epidx %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Attempted operation on an SMC port that is not initialized"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-4-PORT_INIT_ERR

SEVERITY: Error

FORMAT: "%s, line %d: Port %d already initialized on Epidx %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Attempted initialization of a port that is already initialized"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-4-RMT_CTXT_ERR

SEVERITY: Error

FORMAT: "%s, line %d: Error %s on Epidx %d, Port %d, rmtEpid 0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "The specified error occurred while trying to create a context for a remote 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.

SHMA-4-RETX_Q_ERR

SEVERITY: Error

FORMAT: "%s, line %d, operation %s: error 0x%x on Epidx %d Retransmission Q"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error operating on Epidx 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.

SHMA-4-MSG_FREE_ERR

SEVERITY: Error

FORMAT: "Error 0x%x freeing an RMI message"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error operating on Epidx 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.

SHMA-5-MSG_DUP_ERR

SEVERITY: Warning

FORMAT: "%s, line %d, Message dup failed, error 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Resource depletion problem. Use ssiChunkPoolShow to determine the state of the mblk pool"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-MSG_MALLOC_ERR

SEVERITY: Warning

FORMAT: "%s, line %d, Message dupallocation failed, error 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Resource depletion problem. Use ssiChunkPoolShow to determine the state of the mblk / data buffers pools"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-INV_MSG_PARAM

SEVERITY: Warning

FORMAT: "%s, line %d, Invalid incoming message header parameter %s, value %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Incoming message failed RMI message header validation"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-5-INV_MSG_TYPE

SEVERITY: Warning

FORMAT: "%s, line %d, Invalid message type %d, Epidx %d, Port %d, srcEpid 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Incoming message failed RMI message header validation"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-7-API_RS_REPORT

SEVERITY: Information

FORMAT: "%s: AppId 0x%x, tId 0x%x, tName %s , Ref. pslot %d, callerPc 0x%x, evtNum 0x%x"

FLAG: Stack Trace|Write Bram

THROTTLING: No Throttling

EXPLANATION: "Info on caller to a SHM resource report API"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-7-FATAL_ERR_RPT

SEVERITY: Information

FORMAT: "%s: AppId 0x%x, tId 0x%x, tName %s , Ref. pslot %d, callerPc 0x%x, evtNum 0x%x"

FLAG: Stack Trace|Write Bram

THROTTLING: No Throttling

EXPLANATION: "Info on caller to a SHM fatal error resource report API"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-7-FRUMISMATCH_RPT

SEVERITY: Information

FORMAT: "AppId 0x%x,tId 0x%x,tName %s,pslot %d,bay# %d callPc 0x%x,BcCnfState

FLAG: Stack Trace|Write Bram

THROTTLING: No Throttling

EXPLANATION: "Info on caller to a BackCard FRU Mismatch State Change report API"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-7-RESCDTYPE_SET_R

SEVERITY: Information

FORMAT: "ApId:0x%x,tId 0x%x,psl %d,callPc 0x%x,ChOp %d,CurBc %d,NewFc %d,CurBoBC %d,NewBoBC %d,CurToBC %d,NewToBC %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Info on caller to a SHM Reserved Card Type Set request API"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHMA-7-INVALID_PARAMS

SEVERITY: Information

FORMAT: "Invalid Parameters %s,"

FLAG: Write Bram

THROTTLING: No Throttling

EXPLANATION: "Info on caller to a SHM API that the parameters are invalid."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS : "rpmxf-traps"

TRAP-4-TRAPCL_COMEP

SEVERITY: Error

FORMAT: "Creation of EPID \"%s\" failed rc= 0x%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The ssiIpcComEpCreate() function failed. return code(rc) denotes the task EPID in hex. This event indicates a problem with SSI or the system is running low on memory or there is a hardware problem"

RECOMMENDED ACTION: An internal system error has occurred. Please collect the data mentioned in the REQUIRED_INFO section and call your Cisco techinal representative (TAC).

REQUIRED INFO: Capture the output from the following CLI commands:

a) dsptask 0 2

b) dsplog

c) dsperr

d) memShow

e) dspcds

f) dsprevs

g) dspversion

h) dspdate

TRAP-5-TRAPCL_BINDEP

SEVERITY: Warning

FORMAT: "Binding name to EPID \"%s\" failed rc= 0x%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Trap Client Epid Registration in global table failed"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-4-TRAPCL_TIMER_CR

SEVERITY: Error

FORMAT: "Creation of timer failed rc= 0x%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to create a synchronous timer. Possible problem with SSI or low memory"

RECOMMENDED ACTION: An internal system error has occurred. Please collect the data mentioned in the REQUIRED_INFO section and call your Cisco techinal representative (TAC).

REQUIRED INFO: Capture the output from the following CLI commands:

a) dsptask 0 2

b) dsplog

c) dsperr

d) memShow

e) dspcds

f) dsprevs

g) dspversion

h) dspdate

TRAP-4-TRAPCL_ATTHDLR

SEVERITY: Error

FORMAT: "Attaching of handler \"%s\" failed Epid = 0x%08X rc= 0x%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Attaching of a handler to an trap client EPID has failed. It shows a problem with IPC. Trapclient subsystem may not work"

RECOMMENDED ACTION: An internal system error has occurred. Please collect the data mentioned in the REQUIRED_INFO section and call your Cisco techinal representative (TAC).

REQUIRED INFO: Capture the output from the following CLI commands:

a) dsptask 0 2

b) dsplog

c) dsperr

d) memShow

e) dspcds

f) dsprevs

g) dspversion

h) dspdate

TRAP-4-TRAPCL_INTQ_FRE

SEVERITY: Error

FORMAT: "Failed to free memory. Invalid ptr in \"%s\" type= \"%s\" rc= 0x%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to free allocated IntQ memory. It shows a problem with SSI"

RECOMMENDED ACTION: An internal system error has occurred. Please collect the data mentioned in the REQUIRED_INFO section and call your Cisco techinal representative (TAC).

REQUIRED INFO: Capture the output from the following CLI commands:

a) dsptask 0 2

b) dsplog

c) dsperr

d) memShow

e) dspcds

f) dsprevs

g) dspversion

h) dspdate

TRAP-5-TRAPCL_INTQ_ALL

SEVERITY: Warning

FORMAT: "Memory allocation of element failed in \"%s\" type= \"%s\" size = %d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to create a fixed size memory chunk manager pool for internal queue elements. It shows that either a) there is a problem with SSI b) there is not enough memory"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_INTQ_GET

SEVERITY: Warning

FORMAT: "Retrieval of element off the Queue failed in \"%s\" reason= \"%s\" Qsize = %d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An attempt was made to retreive an element off the head of a queue, while the queue was empty"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-4-TRAPCL_FREE

SEVERITY: Error

FORMAT: "Free failed in \"%s\" type= \"%s\" rc= 0x%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to free an IPC message. It shows a problem with IPC"

RECOMMENDED ACTION: An internal system error has occurred. Please collect the data mentioned in the REQUIRED_INFO section and call your Cisco techinal representative (TAC).

REQUIRED INFO: Capture the output from the following CLI commands:

a) dsptask 0 2

b) dsplog

c) dsperr

d) memShow

e) dspcds

f) dsprevs

g) dspversion

h) dspdate

TRAP-5-TRAPCL_BAD_MSGF

SEVERITY: Warning

FORMAT: "Unknown message field in \"%s\" type sent= %d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "A message was received from the server on the controller card, with unknown message field. It was supposed to be either an ACK or a NACK"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_TMR_SCHD

SEVERITY: Warning

FORMAT: "failed to schedule timer in \"%s\" timeout value = %d, timer type = %d, rc= 0x0%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to schedule a timeout event: it could be either of three

a) acknowledgement timer

b) send timer

c) server unavailable timer. It shows a problem with SSI"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_TMR_CNCL

SEVERITY: Warning

FORMAT: "failed to cancel timer in \"%s\" timer type = %d, rc= 0x0%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to cancel a previously scheduled timeout timer for trapClient. This problem shows a problem with SSI"

RECOMMENDED ACTION: An internal system error has occurred. Please collect the data mentioned in the REQUIRED_INFO section and call your Cisco techinal representative (TAC).

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_INV_SEQN

SEVERITY: Warning

FORMAT: "Incorrect seq number received in \"%s\" expected = %d, msg seqnum = %d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An error occurred in the function that handles ACK messages from the server. An incorrect message seq number was received."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_FLUSHEP

SEVERITY: Warning

FORMAT: "Error flushing EPID %d name=\"%s\" in \"%s\" rc= 0x0%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to flush ( i.e. remove all messages ) of the EPID failed. It can happen because a) the EPID is invalid b) the queue on the EPID is inconsistent c) Failed to free queue element. It shows a problem with IPC"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_BADEP

SEVERITY: Warning

FORMAT: "Invalid Epid %d epid name=\"%s\"."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An invalid EPID identifier for the incoming messages to the trapClient"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_INVSLOT

SEVERITY: Warning

FORMAT: "Invalid Controller logical slot in \"%s\"."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An invalid logical slot for the active controller card was returned by CTC. It was required by trapClient in order to resolve the EPID of the trap server. "

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_SENDERR

SEVERITY: Warning

FORMAT: "Error Sending IPC message to Epid= %d rc= 0x0%08X"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An attempt to send an asynchronous IPC message to the server's EPID failed. It failed because of problems with IPC which could be that the communication path to the remote card is broken or EIPD on the local card doesn't exist etc"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-5-TRAPCL_DUPERR

SEVERITY: Warning

FORMAT: "Error Sending dupping IPC buffer s \"%s\" buffer type = %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Trapclient application failed to make a duplicate copy of the message in the rexmit buffer. This is used for message retransmissions, avoiding copying. Its failure shows problem with IPC"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-4-TRAPCL_ASSIGNEP

SEVERITY: Error

FORMAT: "Reassign of EPID \"%s\" failed rc= 0x%08X."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An attempt to assign a new owner task (trapclient) to a communcation EPID, without flushing the message queues, failed. Trapclient may not function."

RECOMMENDED ACTION: An internal system error has occurred. Please collect the data mentioned in the REQUIRED_INFO section and call your Cisco techinal representative (TAC).

REQUIRED INFO: Capture the output from the following CLI commands:

a) dsptask 0 2

b) dsplog

c) dsperr

d) memShow

e) dspcds

f) dsprevs

g) dspversion

h) dspdate

TRAP-7-TRAPCL_DROPPED

SEVERITY: Information

FORMAT: "%s trap client current state = %d; Trap number dropped = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The trapclient task had to drop an incoming message. It can happen because of these two reasons a) trapclient is in INACTIVE state b) trapclient has hit the High Water Mark of the internal queue limit, requiring cleanup and a need to send Lost Trap (seq=0) to the server"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No information is required.

TRAP-4-TRAPCL_NAMESIZE

SEVERITY: Error

FORMAT: "Size of buffer to hold the name of the task creating the EPID is less than required."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The function to create EPID and associate it with the calling task failed. It tried to create a unique task name to be used for creating the EPID. The number of characters in the task name exceeded the set limit. Trapclient may not function."

RECOMMENDED ACTION: An internal system error has occurred. Please collect the data mentioned in the REQUIRED_INFO section and call your Cisco techinal representative (TAC).

REQUIRED INFO: Capture the output from the following CLI commands:

a) dsptask 0 2

b) dsplog

c) dsperr

d) memShow

e) dspcds

f) dsprevs

g) dspversion

h) dspdate

TAPI-4-INVALIDINPUT

SEVERITY: Error

FORMAT: "One of the inputs to the function %s() was invalid."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for one of the parameters passed in as an argument to the named function was invalid."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-5-PARMOUTOFTRANGE

SEVERITY: Warning

FORMAT: "Parm %s is out of range. The range is between %d and %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for the named parameter is out of range."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-4-PARMINVALID

SEVERITY: Error

FORMAT: "Parm %s value '0x%x' is invalid to %s."

FLAG: No Flag

THROTTLING: One Tick

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

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-4-PARMINVLENGTH

SEVERITY: Error

FORMAT: "Parm %s invalid length of %d to %s. Max=%d Value='%s'"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The named paramater passed in as an argument to the named function either had a length of zero or exceeded the maximum value specified."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-4-FUNCFAIL_STKDUM

SEVERITY: Error

FORMAT: "%s() : SNMP subsystem call to %s() failed. rc=%d."

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "The specified function call failed. It failed with the specified return code. A stack trace was generated. If this error is caused because of an error returned by tapiEnterpriseTrapMake(), the following could be some reasons :

a) Slotnumber passed is invalid

RECOMMENDED ACTION: "The system should clean up itself and send out a lost trap. If the problem persists, call TAC."

REQUIRED INFO: " Capture the folowing data:

a) dspdate

TAPI-5-INVALIDNUM

SEVERITY: Warning

FORMAT: "Number of TrapVbs %d is invalid or the linked list is not null-terminated for %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-5-QUEUEFULL

SEVERITY: Warning

FORMAT: "Could not send trap %d from slotnum %d."

FLAG: No Flag

THROTTLING: Five Seconds

EXPLANATION: "The Trap Client Queue has reached/passed the high water mark"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-5-INVOIDPTR

SEVERITY: Warning

FORMAT: "Invalid oid_ptr at line %d: tapiCurPtr= 0x%x , DataPtr= 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "While attempting to pack varbinds into the IPC message, there was a NULL pointer passed for the oid_ptr. The calling application has passed invalid set of parameters to the API to pack the varbinds into an IPC message. This corrupt/ invalid trap structure will not be sent to the server."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-5-INVPTR

SEVERITY: Warning

FORMAT: "Invalid ptr at line %d: %s= 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "While attempting to pack varbinds into the IPC message, there was a NULL pointer passed. The calling application has passed invalid set of parameters to the API to pack the varbinds into an IPC message. This corrupt/ invalid trap structure will not be sent to the server."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-5-INVLENGTH

SEVERITY: Warning

FORMAT: "Invalid OID Length at line %d: length = %d :max allowed = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "While attempting to pack varbinds into the IPC message, there was an invalid OID length passed. The calling application has passed invalid set of parameters to the API to pack the varbinds into an IPC message. This corrupt/ invalid trap structure will not be sent to the server."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-5-DATAPTRGET_ERR

SEVERITY: Warning

FORMAT: "SSI_IPC_DATAPTR_GET returned null at line %d for pMblk= 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "While attempting to pack varbinds into the IPC message, there was a NULL pointer passed. The calling application has passed invalid set of parameters to the API to pack the varbinds into an IPC message. This corrupt/ invalid trap structure will not be sent to the server."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-7-TRAPLET_ERR

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "generic error for Traplets"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TAPI-7-IPC_ERR

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "generic error for Traplets"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS : "rpmxf-sw"

VSIC-5-VSICGENERR

SEVERITY: Warning

FORMAT: "VSICORE: %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "VSICORE: General errors"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VSIC-2-VSIMAJORERR

SEVERITY: Major Alert

FORMAT: "%s, Vsi Major Alert: %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "This error gets logged to indicate TCB error or error upda- ting connections. It may indicate that some connections are not programmed correctly "

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: 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

VSIS-5-VSISERR

SEVERITY: Warning

FORMAT: "VSI Error: %s"

FLAG: Stack Trace

THROTTLING: One Minute

EXPLANATION: "VSIS: General errors"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Flag

VSIS-5-GENERR

SEVERITY: Warning

FORMAT: "%s, line %d: Vsi Slave %s error"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "This is an internal error reported by the VSIS module. It indicates the error could be associated with SSI or IPC."

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

VSIS-5-GENERR_NUM

SEVERITY: Warning

FORMAT: "%s, line %d: Vsi Slave %s error, info=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "This error indicates an error related to CTC events with respect to the card or the PNNI/TAG 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

VSIS-5-GENERR_STR

SEVERITY: Warning

FORMAT: "%s, line %d: Vsi Slave %s error, info=%s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "This error indicates an error related to CTC events with respect card role"

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

VSIS-5-INITERR

SEVERITY: Warning

FORMAT: "%s, line %d: Vsi Slave %s Init error, %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "This is an internal error reported by the VSIS module. This indicates that VSI task was not initialized properly"

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

VSIS-5-TASKSTATE

SEVERITY: Warning

FORMAT: "%s, line %d: VSI TaskState:%s: <%s> --> <%s>"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is an internal error reported by the VSIS module. It indicates an error associated with VSI task"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: 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

VSIS-5-CTCLOGPLFM

SEVERITY: Warning

FORMAT: "%s, line %d: evt=%s, lslot=%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "CTC Log for VSIS Module."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Flag

VSIS-5-CTCLOGCD

SEVERITY: Warning

FORMAT: "%s, line %d: evt=%s, lslot=%d, pslot=%d, redPslot=%d, qual=%d, ChgRn=%d, cdRole=%s(%d)"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "CTC Log for VSIS Module."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Flag

VSIS-5-CTCLOGCNTRL

SEVERITY: Warning

FORMAT: "%s, line %d: evt=%s, loc:%d, slot:%d, Id:%d, type:%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "CTC Log for VSIS Module."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Flag

VSI_-5-VSIRMERR

SEVERITY: Warning

FORMAT: "VSI_VRM Error: %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error messages from VSI RM Module."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VSI_-5-GENERR

SEVERITY: Warning

FORMAT: "%s, line %d: Vsis RM error <%s>"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "General Error messages from VSIS RM Module."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VSI_-5-GENERR_NUM

SEVERITY: Warning

FORMAT: "%s, line %d: Vsis RM error <%s>, info=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "General Error messages from VSIS RM Module (with extra number debug info)."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VSI_-5-GENERR_NUM2

SEVERITY: Warning

FORMAT: "%s, line %d: Vsis RM error <%s>, info=%d %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "General Error messages from VSIS RM Module (with extra number debug info)."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VSI_-5-GENERR_STR

SEVERITY: Warning

FORMAT: "%s, line %d: Vsis RM error <%s>, info=%s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "General Error messages from VSIS RM Module (with extra string debug info)."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS : "rpmxf-ctc"

ZTC-4-EMPTYMSG

SEVERITY: Error

FORMAT: "The message buffer is empty. \n, %s, line %d "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: " The message buffer is empty."

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

ZTC-4-MEMALLOCERROR

SEVERITY: Error

FORMAT: "ssiIpcMessageAllocateFailed. \n, %s, line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "ssiIpcMessageAllocateFailed."

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

ZTC-4-MEMFREEFAIL

SEVERITY: Error

FORMAT: "Failed to free memory. \n, %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to free memory."

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

ZTC-4-MSGRPLYERROR

SEVERITY: Error

FORMAT: "Failed to reply sync message. \n, %s, line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to reply sync message."

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

ZTC-4-EPINSTFAIL

SEVERITY: Error

FORMAT: "Failed to instantiate end point \n, %s, line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to instantiate the specified End Point 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: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

ZTC-4-HDLRATTACHERR

SEVERITY: Error

FORMAT: "Failed to attach message handler \n, %s, line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to attach message 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: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

ZTC-4-PROCERROREXIT

SEVERITY: Error

FORMAT: "Process terminates when it should not \n, %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Process terminate when it should not."

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

ZTC-4-GENERR

SEVERITY: Error

FORMAT: "RPM-XF CTC module error message. \n, %s, line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "RPM-XF CTC module error message. \n, %s, line %d"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

ZTC-4-UNKNOWNMSG

SEVERITY: Error

FORMAT: "Unknown message type. \n, %s, line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Unknown message type. "

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZTC

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech(on RPM-XF)

7. shmCsmTraceShow <slot#> (on PXM shell)

8. sh rpm ctc last-ctc-evt (on RPM-XF)

9. sh rpm ztc shm-evt-hist (on RPM-XF)

DDTS : "rpmxf-alarms"

ZAM-4-EPRESOLVEFAIL

SEVERITY: Error

FORMAT: "Failed to resolve end point %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to resolve end point"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-EPBINDFAIL

SEVERITY: Error

FORMAT: "Failed to bind end point %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to bind end point"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-NOMEM

SEVERITY: Error

FORMAT: "Failed to create memory chunk for alarm manager %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to create memory chunk"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-MALLOCFAIL

SEVERITY: Error

FORMAT: "Failed to allocate memory. %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to allocate memory"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-MEMFREEFAIL

SEVERITY: Error

FORMAT: "Failed to free memory. %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to free memory"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-GENERR

SEVERITY: Error

FORMAT: "%s, line %d: ZAM error <%s>"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "General error message coming from ZAM task"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-COMEPCREATEFAIL

SEVERITY: Error

FORMAT: "%s, line %d:"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to create 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: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-MSGHDLRATACHFAI

SEVERITY: Error

FORMAT: "Failed to attach message handler. %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to attach message 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: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-TIMERCREATEFAIL

SEVERITY: Error

FORMAT: "Failed to create timer. %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to create 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: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-SSITIMERFAIL

SEVERITY: Error

FORMAT: "Failed to create timer. %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "ssiSynchTimerCreate failed"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-SCHEDTIMEOUTFAI

SEVERITY: Error

FORMAT: "Failed to schedule time out. %s, line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to schedule time out"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-BADTIMERKEY

SEVERITY: Error

FORMAT: "Invalid timer key. %s, line %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invalid timer key"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-SSIMESSAGEFAIL

SEVERITY: Error

FORMAT: "SSI message call failed. %s, line %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SSI message call failed"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-CANTREACHNAM

SEVERITY: Error

FORMAT: "Failed to communicate NAM. %s, line %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to communicate NAM"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-NOALARMSUMMARY

SEVERITY: Error

FORMAT: "Failed to generate card alarm summary. %s, line %d "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to generate card alarm summary"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-BADSEVERITY

SEVERITY: Error

FORMAT: "Unknown alarm severity level. %s, line %d "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Unknown alarm severity level"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-BADSTATPARAM

SEVERITY: Error

FORMAT: "Invalid status type. %s, line %d "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invalid status type of ZAM operation"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-NOSUCHALARM

SEVERITY: Error

FORMAT: "Error - try to delete alarms not existing. %s, line %d "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error - try to delete alarms not existing"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

ZAM-4-BADALARMLEVEL

SEVERITY: Error

FORMAT: "Error - Unexpected alarm level. %s, line %d "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error - Unexpected alarm"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs:

1. dspcds, dsprevs, dspver

2. dsplog -mod ZAM

3. dsplog -mod FIPC

4. dsplog -mod SSI

5. dsplog -sl <RPM or RPM-XF slot#>

6. sh tech (on RPM-XF)

7. sh rpm eeprom (on RPM-XF)

DDTS "rpm"

RMM-5-NO_IPC_BUFFER

SEVERITY: Warning

FORMAT: "%s%d Could not get IPC buffer."

FLAG: No Flag

THROTTLING: One Tick

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"

RMM-4-PORT_CREATE_ERR

SEVERITY: Error

FORMAT: "Could not create port: %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to create port for communication. This will impact IPC commnunication 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: " On PXM45:

1. dsplog

2. shellcon: rmm_print_stat

3. shellcon: ipc_print_seats

4. shellcon: ipc_print_ports

5. shellcon: rfs_print_stat

6. shellcon: ipcMblkShow

7. shellcon: ipcTaskMblkShow "

RMM-4-SEAT_CREATE_ERR

SEVERITY: Error

FORMAT: "Could not create seat: %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to create seat for communication. This should never happen. This could happen if there is a memory shortage in the system.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: "On pxm45 (From shellconn):- memShow (From normal CLI prompt) ipcMblkShow- IPC Mblk allocation/free stats, ipcTaskMblkShow- IPC Mblk allocation/free status.

RMM-4-SEAT_DELETE_ERR

SEVERITY: Error

FORMAT: "Could not delete seat: %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to delete IPC seat. This may be due to trying to delete the seat which is already deleted. This should never happen and no impact on operations. It will get recovered on its own. If the problem persists, call the 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: "On PXM45 (from shellconn): ipcMblkShow ipcTaskMblkShow rmm_print_stat ipc_print_seats ipc_print_ports "

RMM-4-TASK_SPAWN_ERR

SEVERITY: Error

FORMAT: "Could not spawn task %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to spawn one of the critical RPM related 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 "ERPM"

RMM-5-UNKNOWN_MSG

SEVERITY: Warning

FORMAT: "Unknown message received at %s. Type %d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unknown message received. This is a temporary one and will get self recovered on its own."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RMM-5-INIT_ACK_ERR

SEVERITY: Warning

FORMAT: "Could not ACK init of task %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to ack task init."

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

RMM-4-TASK_INIT_ERR

SEVERITY: Error

FORMAT: "Task initialization failed for %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This will happen when one of the RPM related tasks failed to intialise or failed. This needs to be analysed by the 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: "On pxm45 (From shellconn):- memShow (From normal CLI prompt) ipcMblkShow- IPC Mblk allocation/free stats, ipcTaskMblkShow- IPC Mblk allocation/free status.

RMM-4-CRDACT_WAIT_ERR

SEVERITY: Error

FORMAT: "Wait for card ACTIVE failed for %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to wait for the RPM card to go ACTIVE. This should never happen. If it happens, it will be an internal error. This needs to be analysed by TAC team 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"

RMM-4-UNREACHABLE

SEVERITY: Error

FORMAT: "Unreachability violation in %s:%d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unexpected seat transport_type while sending the IPC message between RPM and PXM. This is an internal error. This will affect the commnuication between PXM and the corresponding RPM slot. Contact TAC for further anaysis on this problem."

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: "Collect the following from PXM: dspsarchans shellcon: rmm_print_stat shellcon: ipc_print_seats shellcon: ipc_print_ports shellcon:scmCardShow <slot#> Collect the following from RPM: show tech show proc cpu debug atmdx heartbeat. "

RMM-7-RESYNC_SUCCESS

SEVERITY: Information

FORMAT: "RMM seat resync success!!"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "RMM seat resync success!!"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RMM-4-SEAT_RESYNC_ERR

SEVERITY: Error

FORMAT: "RMM seat resync failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This might happen when PXM unable to resync seats with RPM during switch-over. This needs to be anlaysed by TAC and possibly 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: "Collect the following from PXM: shellcon: rmm_print_stat shellcon: ipc_print_seats shellcon: ipc_print_ports shellcon:scmCardShow <slot#>."

RMM-4-SEAT_NOT_UP

SEVERITY: Error

FORMAT: "Seat not up to %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This error happens when not able to create a seat for commnuication with RPM or not able to resync seat during switch-over. This will get recovered on its own by resetting the corresponding RPM card. If problem still exists, 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: "Collect the following from PXM: shellcon: rmm_print_stat shellcon: ipc_print_seats shellcon: ipc_print_ports "

RMM-4-INIT_FAILURE

SEVERITY: Error

FORMAT: "Initialization failure %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This happens when one of the critical RPM related task on PXM fails to intialise some of its components. PXM switchover might clear this problem. This is an internal error. If it still happens it needs to be analysed 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"

RMM-5-BAD_NUM_VALUE

SEVERITY: Warning

FORMAT: "%s%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unexpected numeric value or return code."

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

RMM-5-BAD_STR_VALUE

SEVERITY: Warning

FORMAT: "%s%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unexpected string value or return code."

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

RMM-5-IPC_SEND

SEVERITY: Warning

FORMAT: "%s%s%d IPC error occurred."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to send ipc packet to RPM."

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

RMM-5-NO_SSI_BUF

SEVERITY: Warning

FORMAT: "%s%d Failed to get SSI buffer."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to get SSI Buffer."

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

REQUIRED INFO: No Required Info

RMM-4-NULL_PTR

SEVERITY: Error

FORMAT: "%s%d Received a NULL pointer."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Received a NULL pointer. This happens due to insufficient memory available in the system.This might be a temporary incident. If it persists, contact the 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 "ERPM"

RMM-4-GEN_ERR

SEVERITY: Error

FORMAT: "%s:%d: An unexpected error occurred."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An unexpected internal error occurred in one of the RPM related task running on PXM. 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: " On PXM45:

RMM-4-MSG_SEND_ERR

SEVERITY: Error

FORMAT: "%s:%d: Failed to send intercard/intertask message."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to send intercard/intertask message sent by RPM. This might impact the redundancy function of RPM if the problem still exists. Mostly it happens due to some internal state error of the system. 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: "On PXM45 (from shellcon): ssiMsgQList ssiSemList "

RMM-7-CLRALLCNF

SEVERITY: Information

FORMAT: "RPM Slot %d does not support clrAllCnf. Slot %d config will be cleared."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "RPM slot does not support clrAllCnf"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RMM-4-CLRALLCNF_ERR

SEVERITY: Error

FORMAT: "ClrAllCnf failed for RPM Slot %d (errno = %d)"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error happened while doing a clrallcnf on a shelf. This normally happens when unable to open or create auto_config of the RPM slot in C:/RPM directory. This will impact clrallcnf for one or more RPM slots. Contact TAC representative for further resolution."

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"

RMM-4-GEN_ERROR

SEVERITY: Error

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "For logging all RMM related errors"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RMM-5-GEN_WARNING

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "For logging all RMM related warnings"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RMM-6-GEN_NOTICE

SEVERITY: Notice

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "For logging all RMM related notices"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RMM-7-GEN_INFO

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "For logging all RMM related info messages"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RMM-4-CSR_MSG_PROC_ER

SEVERITY: Error

FORMAT: "Message Processing Error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error happened while processing RPM CLRSMCNF message."

RECOMMENDED ACTION: "Indicates an internal error detected by the PXM RMM module which handles clrsmcnf requests.It needs to be analyzed by TAC and possibly by the development team."

REQUIRED INFO: "Collect dsplog, dsperr information"

RMM-4-CSR_IPC_COMEP_C

SEVERITY: Error

FORMAT: "CSR IPC comm endpoint create error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not able to create IPC commnunication endpoint to intercept messages from Clear/Save/restore commands to RMM."

RECOMMENDED ACTION: "Indicates an internal error detected by the PXM RMM module which handles clrsmcnf requests.It needs to be analyzed by TAC and possibly by the development team."

REQUIRED INFO: "Collect dsplog, dsperr information"

RMM-4-CSR_IPC_HDLR_ER

SEVERITY: Error

FORMAT: "CSR IPC comm endpoint handler attach error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not able to attach IPC commnunication handler to intercept messages from Clear/Save/restore commands to RMM."

RECOMMENDED ACTION: "Indicates an internal error detected by the PXM RMM module which handles clrsmcnf requests.It needs to be analyzed by TAC and possibly by the development team."

REQUIRED INFO: "Collect dsplog, dsperr information"

RMM-4-STBY_SYNC_ERR

SEVERITY: Error

FORMAT: "ClrAllCnf sync to standby failed for RPM/RPM-XF Slot %d (errno = %d)."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error happened while doing the clrallcnf file sync-up to standby on a shelf. This clrallcnf file (auto_config_slot_xx) is created as part of the execution of clrallcnf/clrsmcnf. Contact TAC representative for further resolution."

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"

RMM-4-TMPCOPY_ERR

SEVERITY: Error

FORMAT: "Creating Temporary ClrAllCnf file (for syncup to standby) failed for RPM/RPM-XF Slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error happened while creating the clrallcnf temp file auto_config_slot_xx to auto_config_slot_xxRMMCLRCNF. This activity is as part of sync-up of the clrallcnf file to standby during clrallcnf/clrsmcnf. Contact TAC representative for further resolution."

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"

RMM-4-FILE_STAT_ERR

SEVERITY: Error

FORMAT: "Failed to get the auto_config file status on standby PXM for RPM/RPM-XF Slot %d (errno=%d)."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error happened when standby fails to get the status of auto_config_slot file for this slot in its local disk. When standby comes up, it deletes the auto_config file that doesn't exist on active. This happens only When clrallcnf or clrsmcnf was attempted last on the active PXM and the standby is inserted after that. Deletion of auto_config_file on standby will fail if this error happens."

RECOMMENDED ACTION: "Re-insert the standby PXM again and see whether the auto_config (that doesn't exist on active) is getting deleted. If not during the second time, contact TAC representative for further resolution."

REQUIRED INFO: Capture the following and contact your technical support representative.

a) dspcds

b) dspcd

c) dsperr

d) dsplog

e) dspred

f) dir "ERPM"

RMM-4-FILE_DELETE_ERR

SEVERITY: Error

FORMAT: "Failed to remove the auto_config file on standby PXM disk for RPM/RPM-XF Slot %d (errno=%d)."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error happened when standby fails to delete the auto_config_slot file for this slot in its local disk. When standby comes up, it deletes the auto_config file that doesn't exist on active. This happens only When clrallcnf or clrsmcnf was attempted last on the active PXM and the standby is inserted after that. Deletion of auto_config_file on standby will fail if this error happens."

RECOMMENDED ACTION: "Re-insert the standby PXM again and see whether the auto_config (that doesn't exist on active) is getting deleted. If not during the second time, contact TAC representative for further resolution."

REQUIRED INFO: Capture the following and contact your technical support representative.

a) dspcds

b) dspcd

c) dsperr

d) dsplog

e) dspred

f) dir "ERPM"

RMM-4-CTC_EVT_TX_FAIL

SEVERITY: Error

FORMAT: "Failure in Tx evt %s (%d) to %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This error happens when PXM is not able to send CTC event to RPM-XF 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: Capture the following and contact your technical support representative.

a) dspcds

b) dspcd

c) dsperr

d) dsplog

e) dspred

f) dir "ERPM"

RMM-5-CTC_PORT_OPEN_F

SEVERITY: Warning

FORMAT: "Could not open port - %s to Tx %s (%d)"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This warning is expected during PXM switchover. RPM-XF takes care to be in sync with respect to these events after receiving the switchover message. If this warning is seen other than in a PXM switchover scenario, then this needs to be looked at by TAC."

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"

RMM-7-SWITCHOVER_NOTI

SEVERITY: Information

FORMAT: "Switchover Notification Sent to Slot %d;Retry Counter %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "PXM switchover notification to RPM for the slot"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RMM-4-MAX_RETRY_SWITC

SEVERITY: Error

FORMAT: "Max Switchover Notifications Sent to the Slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Maximum switchover notifications sent to the RPM slot"

RECOMMENDED ACTION: No action required

REQUIRED INFO: "On PXM:

1. dsplog

2. rmm_print_seat_table on PXM shell

On RPM:

1. sh ver

2. sh rpm card

3. sh ipc ports "

DDTS "pxm-connmgm"

RCMP-4-INIT_ERR

SEVERITY: Error

FORMAT: "rpDriverInit Error exit due to %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "rpDriverInit routine failed."

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

REQUIRED INFO: No Required Info

RCMP-7-GEN_ERR

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "General Error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RCMP-7-ADD_CON_ERR

SEVERITY: Information

FORMAT: "%s %u"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error while adding connections."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RCMP-7-SRAM_ERR

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Static RAM read/write error occured."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

DDTS "rpm"

RVT-4-INIT_ERROR

SEVERITY: Error

FORMAT: "Init Error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is an internal error happened when one of the RPM line module related tasks failed to come up. This needs to be analysed 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"

the platform engineer."

RVT-4-INIT_SYNCH_TIME

SEVERITY: Error

FORMAT: "rvtSynchTimerId creation error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is an internal error happened during one of the RPM line module related feature initialisation. This needs to be analysed 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"

RVT-4-INIT_CONN_ALARM

SEVERITY: Error

FORMAT: "Connection Alarm File Initialization Error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is an internal error happened during one of the RPM line module related feature initialisation. This needs to be analysed 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"

RVT-7-SWAMPING

SEVERITY: Information

FORMAT: "%s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Event occurred during swamping condition."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RVT-4-SWAMPING_ERROR

SEVERITY: Error

FORMAT: "%s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is an internal error related to RPM service module. This needs to be analysed 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"

RVT-4-IOS_ERROR

SEVERITY: Error

FORMAT: "IOS IPC Error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An IPC error had occurred. if it is due to the fact that a NULL data/msg is received. It might be a momentarily one. It will get self recovered. If this error persists or any other event happens, then 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"

RVT-4-BULK_SUBIF_ERR

SEVERITY: Error

FORMAT: "RPM Bulk Update failed for slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This will happen when PXM can't able to update the RPM sub interface information sent by RPM into its database allocated for RPM. This might be due to the fact that the database for that slot is not initialiased yet. 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"

RVT-4-CONN_RESYNC_ERR

SEVERITY: Error

FORMAT: "Conn Resync Error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This error occured during the connection re-sychronisation. This is an internal error and it is momentary one in most of the cases. if it persists, 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"

RVT-4-SNMP_ERROR

SEVERITY: Error

FORMAT: "Snmp Error %s %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This SNMP error had occurred when failed to

a) bring up the SNMP task which handles all the

SNMP requests for RPM.

b) Not able to establish commnunication endpoint

to service the SNMP requests. This should never happen and if it persists, then this should be analysed by TAC and 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"

RVT-4-SNMP_CONN_ERR

SEVERITY: Error

FORMAT: "Snmp Error%s ifIndex%d vpi%d vci%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This SNMP error had occurred when failed to

a) bring up the SNMP task which handles all the

SNMP requests for RPM.

b) Not able to establish commnunication endpoint

to service the SNMP requests. This should never happen and if it persists, then this should be analysed by TAC and 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"

RVT-4-INIT_FEATURE_CO

SEVERITY: Error

FORMAT: "Config Copy Initialization Error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is an internal error happened during one of the RPM line module related feature initialisation. This needs to be analysed by TAC and possibly by the development team. The implication of this issue is that the user will not be able to use the Config-Copy feature completely - Th erow entries of ConfigCopy feature cannot be aged. The user may have destroy the rows manually after the Config Copy operation is finished."

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"

RVT-7-CONFIG_COPY_EVE

SEVERITY: Information

FORMAT: "Config Copy Event slot %d - %s %s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is a Config Copy Event. The events could be one of the following

1) ConfigCopy set request sent successful.

2) Config Copy response from RPM write mem successful."

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"

RVT-5-CONFIG_COPY_FOR

SEVERITY: Warning

FORMAT: "Config Copy WARNING slot %s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is a Warning that a wrong slot number has been passed in for the ccCopyIndex field of a SNMP Config Copy Request."

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"

RVT-5-CONFIG_COPY_FOR

SEVERITY: Warning

FORMAT: "Config Copy WARNING slot %d %s 0x%08x 0x%08x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is a Warning that a wrong ccCopyIndex has been passed in a SNMP Config Copy Request."

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"

RVT-4-CONFIG_COPY_WRI

SEVERITY: Error

FORMAT: "Config Copy WARNING slot %d %s 0x%08x 0x%08x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is an error that the Config Copy (write mem) operation failed on an RPM 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: Capture the following and contact your technical support representative.

a) dspcds

b) dspcd

c) dsperr

d) dsplog

e) dspred

f) dir "ERPM"

RVT-4-SUBIF_SYNC_RAM_

SEVERITY: Error

FORMAT: "Error%s Slot%d Port%d Errno%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This is an error that the RPM subinterface sync ram 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: Capture the following and contact your technical support representative.

a) dspcds

b) dspcd

c) dsperr

d) dsplog

e) dspred

f) dir "ERPM"

DDTS "drivers"

SABR-2-SA_INIT_ERR

SEVERITY: Major Alert

FORMAT: "SABRE Init Err line %d, errno=0x%X 0x%X,0x%X"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Indicates an internal error detected by the SABRE 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 "

SABR-2-SA_INIT_ERR_STR

SEVERITY: Major Alert

FORMAT: "SABRE Init Err line %d, errno=0x%X 0x%X,%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Indicates an internal error detected by the SABRE 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 "

SABR-4-SA_HW_ERR

SEVERITY: Error

FORMAT: "SABRE Err line %d, errno=0x%X 0x%X,0x%X"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Indicates an hardware error detected by the SABRE 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

2. do core dump or register dump

3. dspchancnt on affected connection"

SABR-4-SA_HW_ERR_STR

SEVERITY: Error

FORMAT: "SABRE Err line %d, errno=0x%X 0x%X,%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Indicates an hardware error detected by the SABRE 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

2. do core dump or register dump

3. dspchancnt on affected connection"

SABR-5-SA_WARN

SEVERITY: Warning

FORMAT: "SABRE Warning line %d, errno=0x%X 0x%X,0x%X"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Indicates an warning detected by the SABRE driver."

RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"

REQUIRED INFO: " On 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

6. do core dump or register dump "

SABR-5-SA_WARN_STR

SEVERITY: Warning

FORMAT: "SABRE Warning line %d, errno=0x%X 0x%X,%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Indicates an warning detected by the SABRE driver."

RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"

REQUIRED INFO: " On 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

6. do core dump or register dump "

SABR-7-SA_INFO

SEVERITY: Information

FORMAT: "SABRE Info line %d, errno=0x%X 0x%X,0x%X"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SABRE Informational Event."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SABR-7-SA_HMM_INFO

SEVERITY: Information

FORMAT: "SABRE HMM Info line %d, %s, 0x%08X,0x%08X"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SABRE Informational Event."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR-5-SARQUEUE

SEVERITY: Warning

FORMAT: "SAR QE = %d, frmIsNotInTxQueue=%d"

FLAG: Write Bram

THROTTLING: One Tick

EXPLANATION: "SAR overflow has occurred in QE"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR-1-SAR_FRMFIFO_ERR

SEVERITY: Fatal

FORMAT: "QE1210 Frm FIFO Error. QE: %d "

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "QE1210 Frm FIFO may be out of sync. with frames in SAR Mbin In this case, Rx Fifo, Frm Fifo and SAR Mbin queues must be pruged"

RECOMMENDED ACTION: "if QE1210 Frm FIFO out of sync. can not be resolved by purging the queues, then card reset need to be done"

REQUIRED INFO: "Pls goto shell of the controller cards and collect the infor. using shell command -- sarQe1210IsrShow 0"

SAR-7-PATH_INFO

SEVERITY: Information

FORMAT: "Glcn: %d, Vi-Vpi-Vci: Src %d-%d-%d Dest %d-%d-%d, Tot %d, Len %d"

FLAG: No Flag

THROTTLING: One Minute

EXPLANATION: "Logging path info for debuggin"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "sapi"

SAPI-4-NULLPARAMPTR

SEVERITY: Error

FORMAT: "%s NULL pointer passed as parameter"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Software Error -- Unexpected Null pointer Found"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-INITERROR

SEVERITY: Error

FORMAT: "%s Initialization error!"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "SAPI Failed to initialize communication end point"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

SAPI-4-NOMORESESSIONS

SEVERITY: Error

FORMAT: "%s No more sessions available"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SAPI Failed to initialize a new session, max number of SAPI session reached"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-NULLHANDLERTABL

SEVERITY: Error

FORMAT: "%s Could not allocate Handler Table"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SAPI Failed to initialize a new Handler Table, not enough memory"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

SAPI-4-INVALIDHANDLE

SEVERITY: Error

FORMAT: "%s Invalid SAPI Handle %u"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Software error -- No session associated with current SAPI 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: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-INVALIDREQUESTT

SEVERITY: Error

FORMAT: "%s Invalid Request Type %u"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid request type in SAPI msg"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-NOMESSAGEDATA

SEVERITY: Error

FORMAT: "%s IPC Message with no data %u"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "IPC data pointer in SAPI is NULL"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

SAPI-4-NULLHEADERPARAM

SEVERITY: Error

FORMAT: "%s NULL Header Params Ptr"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Software error -- Unexpected NULL Header Params Pointer in SAPI msg"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-INVHDRPARAMS

SEVERITY: Error

FORMAT: "%s Invalid Header Params for Event. \nCall Ref %d External Ref %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid Header Params in SAPI msg"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-INVHDRPARAMS_SE

SEVERITY: Error

FORMAT: "%s Invalid Header Params for Setup Event. \nCall Ref %d External Ref %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid Header Params in SAPI setup msg"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-NOREQUESTDATA

SEVERITY: Error

FORMAT: "%s Missing associated data for request"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Software error -- SAPI msg parameter is associated with a unexpected Null pointer"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-COULDNOTSENDMSG

SEVERITY: Error

FORMAT: "%s Could not message to client or server %d %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Could not send sapi/ipc msg"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-COULDNOTFREEMEM

SEVERITY: Error

FORMAT: "%s Could not free memory associated with session"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Could not free SAPI handler 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: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

SAPI-4-COULDNOTGETSRVR

SEVERITY: Error

FORMAT: "%s Could get the Ep Id of the SAPI Server %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Could get the Ep Id of the SAPI Server"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

SAPI-4-QINITERROR

SEVERITY: Error

FORMAT: "%s Error %s the %s IPC queue"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "SAPI Failed to initialize IPC queues for communication"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

SAPI-4-IPCERROR

SEVERITY: Error

FORMAT: "%s Error %s IPC Queue %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Generic IPC Errors, Communication between SAPI and Signalling call control may be affected."

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: Please collect the output of CLIs

a) General dspver, depcds, dsplog, dsperr, dspmempart

b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,

c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,

d) Congestion dsppnportcc, dspsvcparm,

e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

DDTS "drivers"

SAR-5-SAR_DMA_ERR

SEVERITY: Warning

FORMAT: "SAR DMA Error %s() qe_no %d, error-id %d, error-loc %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "DMA error has happened."

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

SAR-4-SAR_XMT_ERR

SEVERITY: Error

FORMAT: "SAR Xmt Error %s() glcn %d, frmPtr %p, len %d, offset %d, bufRetOpt %d, error-id %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SAR Xmt error has happened."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SAR-1-SAR_DMA_DEAD

SEVERITY: Fatal

FORMAT: "SAR DMA Freeze : qeno %d, NonEmpty %d, dmaAct %d, Stas3 %x"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "DMA controller Galelio has frozen"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SAR-1-SAR_DMAFRZN_ERR

SEVERITY: Fatal

FORMAT: "DMA Controller Galelio Frozen. QE: %d "

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "DMA controller frozen. Card reset needed for recovery"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SAR-1-SAR_QEINJFRZN_E

SEVERITY: Fatal

FORMAT: "QE1210 INJ Frozen. line: %d QE: %d Status3: %x TaskName: %s DmaSrc: %x DmaLen: %x aal5Hed1: %x aal5Hed2: %x aal5Len: %x"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "QE1210 INJ frozen. Card reset needed for recovery"

RECOMMENDED ACTION: "The card will be reset if QE1210 INJ frozen is more than 20 seconds. After the cared is reset, we should check the log. Msg."

REQUIRED INFO: "This should not continuously happen. if the pxm45 resets continuously, collect dsplog, dsperr, dspver, etc and call TAC"

SAR-1-SAR_QEEXTFRZN_E

SEVERITY: Fatal

FORMAT: "QE1210 EXT Frozen. line: %d QE: %d Status3: %x"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "QE1210 EXT frozen. Card reset needed for recovery"

RECOMMENDED ACTION: "The card will be reset if QE1210 EXT frozen is more than 20 seconds. After the cared is reset, we should check the log. Msg."

REQUIRED INFO: "This should not continuously happen. if the pxm45 resets continuously, collect dsplog, dsperr, dspver, etc and call TAC"

SAR-1-SAROVERFLOW

SEVERITY: Fatal

FORMAT: "SAR overflow %s in QE = %d"

FLAG: Stack Trace|Write Bram

THROTTLING: No Throttling

EXPLANATION: "SAR overflow has occurred in QE"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR-5-SAROVERFLOW

SEVERITY: Warning

FORMAT: "SAR overflow %s in QE = %d"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "SAR overflow has occurred in QE"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR-5-INV_SCHEDULER_F

SEVERITY: Warning

FORMAT: "Invalid sheduler flag %s, QE=%d, scheFlag=0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "The QE scheduler flag is incorrect. When this happens, SAR message transmission or reception may be delayed. After the flag is set again, everything will go to normal."

RECOMMENDED ACTION: No action required

REQUIRED INFO: "Please use dsplog -mod SAR to collect the info. when this problem happens."

SAR-5-SAR_RESET_QE

SEVERITY: Warning

FORMAT: "Reset QE : QE=%d, sts0=%x, sts1=%x, sts2=%x, sts3=%x, gloCnt=%d, reset=%d"

FLAG: Write Bram

THROTTLING: No Throttling

EXPLANATION: "When a QE fatal error such as Free List Empty occurs, we must reset QE chip. During the QE reset, all of incoming cells will be discarded. QE can be recovered after the reset."

RECOMMENDED ACTION: No action required

REQUIRED INFO: "Please use dsplog -mod SAR to collect the info. when this problem happens."

DDTS "drivers"

SAR2-4-INVMAGIC

SEVERITY: Error

FORMAT: "Inv. cnt = %d, s3= %d, numFrm=%d,HCnt=%d, SCnt= %d, QE=%d, Flag=0x%x, notInQ=%d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION : "The specified magic in the specified hader and mblk is not a valid one. It indicates that QE cannot transmit the SAR messages in a specified interval. The retransmission will be started."

RECOMMENDED ACTION: No action required

REQUIRED INFO: "please use dsplog -mod SAR and dsplog -mod SAR2 to collect all of info."

SAR2-5-HDRADDERROR

SEVERITY: Warning

FORMAT: "Error adding Pop1 header to mblk 0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR2-5-MAXLCNERROR

SEVERITY: Warning

FORMAT: "Destination LCN %d out of range. (Max LCN %d)"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR2-5-FRMMAXLENERROR

SEVERITY: Warning

FORMAT: "Frame with %d bytes exceeds max frame length %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR2-5-CELLMAXLENERROR

SEVERITY: Warning

FORMAT: "Cell with %d bytes exceeds max cell length %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR2-5-P1SARDISPERROR

SEVERITY: Warning

FORMAT: "P1 SAR dispatch error msgBlk %x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR2-5-P1SARSNDERROR

SEVERITY: Warning

FORMAT: "P1 SAR send error status %x, errno %x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR2-5-P2INITERROR

SEVERITY: Warning

FORMAT: "P2 SAR initialization error %s errno %x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR2-5-REGERROR

SEVERITY: Warning

FORMAT: "%d P2 SAR registration error LCN 0x%x, errno %x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SAR2-5-SPIERROR

SEVERITY: Warning

FORMAT: "%d spiSarLcnGet error connRef=%d, LCN 0x%x, errno %x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "shm"

SCM-7-MSGQRCV

SEVERITY: Information

FORMAT: "<%s> rcv msg error"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error in receiving message."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SCM-4-SPI_ERROR

SEVERITY: Error

FORMAT: "%s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Spi path addition failed."

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

REQUIRED INFO: 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.

SCM-4-INIT

SEVERITY: Error

FORMAT: "psmScmInit failed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SCM initialization failed."

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

REQUIRED INFO: 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.

SCM-5-UNKNOWN_MSG

SEVERITY: Warning

FORMAT: "unknown msg%-s, msgQid 0x%x, srcId %d, msgFmt %d, msgType 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unknown message type received."

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

SCM-4-SEND_FAIL

SEVERITY: Error

FORMAT: "%s msgType 0x%x msgQid 0x%x msgLen %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SCM ssi mesg send to application failed."

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

REQUIRED INFO: 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.

SCM-4-HTBT_ERROR

SEVERITY: Error

FORMAT: "line %d | errno 0x%x | msg %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SCM error in rpm htbt 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: 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.

SCM-4-OVERSIZE_FRAME

SEVERITY: Error

FORMAT: "Over size frame %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Frame bigger than the expected size received."

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.

SCM-5-UNKNOWN_VALUE

SEVERITY: Warning

FORMAT: "<%s> unknown %s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unknown cardInx value."

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

SCM-5-UNKNOWN_FRAME

SEVERITY: Warning

FORMAT: "unknown frame, msgQid %d, %s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unknown frame received."

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

SCM-5-WRONG_STATE

SEVERITY: Warning

FORMAT: "Wrong state %s slot %d state %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Card is in the wrong state."

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

SCM-4-NULLPTR

SEVERITY: Error

FORMAT: "<%s> Data pointer is NULL"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "NULL pointer encountered."

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.

SCM-5-SCM_Q_OVERFLOW

SEVERITY: Warning

FORMAT: "slot %d priority %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SCM queue overflow."

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

SCM-5-SCM_PRI_ERROR

SEVERITY: Warning

FORMAT: "slot %d priority %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Retransmit queue is empty."

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

SCM-4-NODEST

SEVERITY: Error

FORMAT: "Card %d doesn't exist, %d %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Destination not present."

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.

SCM-4-SEQ_NUM_MISMTCH

SEVERITY: Error

FORMAT: "Mismatched sequence number for slot%d expected %d rcv %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SCM frame sequence number mismatch."

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.

SCM-4-OUT_OF_BUF

SEVERITY: Error

FORMAT: "<%s> Out of buffer"

FLAG: No Flag

THROTTLING: One Minute

EXPLANATION: "SSI frame buffer allocation function returned error."

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.

SCM-4-SAR_RCV

SEVERITY: Error

FORMAT: "Sar Rcv error, rxStatus %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error in receiving SAR buffer."

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

REQUIRED INFO: 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.

SCM-4-SSI_XMT

SEVERITY: Error

FORMAT: "ssiFrameXmt failed, error status %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Frame transmission error."

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.

SCM-4-RESP_TIMEOUT

SEVERITY: Error

FORMAT: "\n SCM Retries %d,State %d, cardNoResp %d and Timeout waiting for response for slot %d, report to PMM"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Response time out."

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.

SCM-5-BAD_SCM_CD_ST

SEVERITY: Warning

FORMAT: "The SCM previous poll card state at pslot %d is invalid. PrevState %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unexpected previous SCM polled card state"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SCM-4-WAITING_FOR_DAC

SEVERITY: Error

FORMAT: "\n SCM Retries %d , State %d at slot %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Waiting for data acknowledgment"

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.

SCM-6-CARD_INSERTION

SEVERITY: Notice

FORMAT: "The Card in Slot %d is Present"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Card Insertion Detected"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SCM-6-RPM_IPC_FAILURE

SEVERITY: Notice

FORMAT: "The RPM in Slot %d is not processing IPC messages"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "RPM IPC Failure. Provisioning or any other SNMP/CLI action on this card may not succeed."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SCM-6-RPM_IPC_RECOVER

SEVERITY: Notice

FORMAT: "The RPM in Slot %d has resumed IPC message processing"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "RPM IPC Recovery"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SCM-6-RPM_NOT_RESPOND

SEVERITY: Notice

FORMAT: "The RPM in Slot %d is not responding and may be faulty."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The RPM is not responding to low level heartbeat messages"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SCM-6-RPM_RESPONDING

SEVERITY: Notice

FORMAT: "The RPM in Slot %d is responding and has recovered."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The RPM is responding to hearbeat messages"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

SCM-4-INVALID_STATE

SEVERITY: Error

FORMAT: "Invalid state %d, scmType %d, instance %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid card state."

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

SCM-4-HTBT_TYPE_BAD

SEVERITY: Error

FORMAT: "Message type bad in Heartbeat Message. Msg Type=%x, RPM Type=%x, RPM State=%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Bad message type received."

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.

SCM-7-PATHCHECK_REPOR

SEVERITY: Information

FORMAT: "badslot%d mypathok=%d tick%ld (pre%d eli%d fail%d unk%d uda%d ure%d) chkpol%d minCds%d minPolls%d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SCM conducted local comm path check"

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.

SCM-7-PATHCHECK_INFO

SEVERITY: Information

FORMAT: "info %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SCM conducted local comm path check"

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

REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Technical support representative.

DDTS "sctfm"

SCTF-7-SYNCRAMERR

SEVERITY: Information

FORMAT: "Sync Ram Error with errno %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal Error. Could occur under normal circumstances. Typical scenario includes reset of standby PXM while bulk/incremental sync is in progress"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SCTF-7-COMEPCREATEFAIL

SEVERITY: Information

FORMAT: " failed to create Epids errno %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal Error. Could occur under normal circumstances. Typical scenario includes reset of standby PXM while bulk/incremental sync is in progress"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SCTF-7-COMEPBIND_FAIL

SEVERITY: Information

FORMAT: " failed to bind Epid errno %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal Error. Could occur under normal circumstances. Typical scenario includes reset of standby PXM while bulk/incremental sync is in progress"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SCTF-7-ILLEGAL_TRANSTI

SEVERITY: Information

FORMAT: " Illegal transition attemped from %d to %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal Error. Could occur under normal circumstances. Typical scenario includes reset of standby PXM while bulk/incremental sync is in progress"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SCTF-7-CNTRLMSGHDLRFAI

SEVERITY: Information

FORMAT: " failed to attach hdlr errno %d, sctFMgrEpId "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal Error. Could occur under normal circumstances. Typical scenario includes reset of standby PXM while bulk/incremental sync is in progress"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SCTF-7-CLIENTMSGHDLRFA

SEVERITY: Information

FORMAT: " failed to attach hdlr errno %d, sctFMgrClientEpId"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal Error. Could occur under normal circumstances. Typical scenario includes reset of standby PXM while bulk/incremental sync is in progress"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SCTF-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 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: No Required Info

SCTF-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

SCTF-6-CTC_EXCEPTION

SEVERITY: Notice

FORMAT: "ctc exception type %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "got a exception in task, collect dsplog,dsperr to know the stack of task "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SCTF-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

SCTF-4-FAILED_DBCREATE

SEVERITY: Error

FORMAT: "Failure Creating SCT DB, Error 0x%x."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Can not create database with disk db manager"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FAILED_TBLCREAT

SEVERITY: Error

FORMAT: "Failure Creating SCT Table, Error 0x%x."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Can not create table in the specified database with the disk db manager"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FAILED_TBLNCHAN

SEVERITY: Error

FORMAT: "Failure register the table, ssiDiskTableRevisionChangeRegisterDone returned error 0x%x"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " the created sctfm table cannot be registered "

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FAILED_DBREGIST

SEVERITY: Error

FORMAT: "Failure Registering SCT Table 0x%x."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Can not register a disk database with the disk db manager"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FAILED_DBWRITE

SEVERITY: Error

FORMAT: "failed to write into sctfm DB table. 0x%x"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Can not write into disk database "

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FAILED_MALLOC

SEVERITY: Error

FORMAT: "errno %d Failed to allocate memory."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Failed to allocate memory., attempt was made to allocate heap memory, but failed, this is a SSI error"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FILE_MISSING

SEVERITY: Error

FORMAT: " Failed to open the file %s errno %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "an attempt was made to open sct file, and that was found missing"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-DIRECTORY_CREAT

SEVERITY: Error

FORMAT: " directory %s created ."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "This is just for information, telling us that a new directory is created on pxm45 HDD"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FAILED_IPCMSG_A

SEVERITY: Error

FORMAT: "errno %d ssiIpcMessageAllocate failed."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Failed to allocate memory for IPC message."

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FAILED_IPCSEND

SEVERITY: Error

FORMAT: "%s_%d ssiIpcMessageSend Failed."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Failed to send IPC message"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-EVENT_INVALID

SEVERITY: Error

FORMAT: "%s_%d event not %s."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unexpected event type detected"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-FAILED_FUNCTION

SEVERITY: Error

FORMAT: "%s_%d %s Failed."

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Internal system error occured."

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-4-IPCDATAPTR_INVA

SEVERITY: Error

FORMAT: " Invalid IPC Data Pointer."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "The pointer to the IPC data is either empty or invalid"

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

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

SCTF-7-INFO_LOG1

SEVERITY: Information

FORMAT: "genral warning %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal error logged for information sake. No action is required"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: "if needed more data can be collected from sctfmHelp on pxm45 shell"

SCTF-7-INFO_LOG2

SEVERITY: Information

FORMAT: "warning %s, %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal error logged for information sake. No action is required"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: "if needed more data can be collected from sctfmHelp on pxm45 shell"

SCTF-7-INFO_LOG3

SEVERITY: Information

FORMAT: "info %s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Internal error logged for information sake. No action is required"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SCTF-7-UNKNOW_FILE

SEVERITY: Information

FORMAT: "unknow file %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "please check if the sct directory has any other file other than sct files "

RECOMMENDED ACTION: "please check the sct folders on the hard disk and remove unwanted files from the csct\axsm area"

REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

DDTS "control-point"

SLFT-4-SLFTST_FAILED

SEVERITY: Error

FORMAT: "Card Fails due to Selftest Failure"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Self test of the card failed."

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

REQUIRED INFO: No Required Info

DDTS "shm"

SHM_-2-UNRES_CD_INSERT

SEVERITY: Major Alert

FORMAT: "SHM INFO: Unreserved Card inserted at slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The SHM detects an unreserved card insertion"

RECOMMENDED ACTION: "This event is logged for attention purpose, no action required. The slot to which the card is inserted is a UNRESERVED slot. slot becomes UNRESERVED when there is no redundancy added or no user traffic is configured."

REQUIRED INFO: No Required Info

SHM_-2-UNRES_CD_REMOVE

SEVERITY: Major Alert

FORMAT: "SHM INFO: Unreserved Card removed at slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The SHM detects a card removal"

RECOMMENDED ACTION: "This event is logged for attention purpuse, no action required. The slot from which the card is removed is a UNRESERVED slot. Slot becomes unreserved when there is no redundancy added or no user traffic is configured."

REQUIRED INFO: No Required Info

SHM_-7-SM_FC_RESERVED

SEVERITY: Information

FORMAT: "Slot %d is reserved for Nvram Id %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "This reports of slot being reserved by SHM"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-NATIVE_CHK_ABRT

SEVERITY: Information

FORMAT: "Card nativity check not performed against slot %d due to backplane read error at slot %d, flag %d"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Card nativity check not performed while this Pxm has H/W mastership"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-4-HMASTER_NO_HREA

SEVERITY: Error

FORMAT: "SHM ERR Hardware mastership error is detected in %s. HMASTER - %s, HREADY - %s. my card health 0x%08x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "hardware mastership error is detected."

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: 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.

SHM_-4-HW_FAILURE

SEVERITY: Error

FORMAT: "SHM ERR Hardware failure is detected in %s. FWREADY is not asserted"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Hardware failure is detected."

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: 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.

SHM_-4-CD_NATIVE_ERR1

SEVERITY: Error

FORMAT: "slot %d BRAM non-native. BP Serial #s actual %s, BRAM %s, Disk %s, health0x%x, Rebuilding from Disk"

FLAG: Stack Trace|Write to Bram

THROTTLING: One Tick

EXPLANATION: "Card Nativity check failed because BRAM is non-native. The card is reset and rebuilt from disk"

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

REQUIRED INFO: Capture the output of the CLI commands, dsperr, dsplog

SHM_-4-CD_NATIVE_ERR2

SEVERITY: Error

FORMAT: "slot %d BRAM and Disk non-native. BP Serial #s actual%s, BRAM %s, Disk %s, health0x%x"

FLAG: Stack Trace|Write to Bram

THROTTLING: One Tick

EXPLANATION: "Card Nativity check failed because the BRAM and disk BP serial numbers match with each other but not with the actual BP Serial Num"

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

REQUIRED INFO: Capture the output of the CLI commands, dsperr, dsplog

SHM_-4-CD_NATIVE_ERR3

SEVERITY: Error

FORMAT: "slot %d Disk non-native. BP Serial #s actual %s, BRAM %s, Disk %s, health0x%x"

FLAG: Stack Trace|Write to Bram

THROTTLING: One Tick

EXPLANATION: "Card Nativity check failed because Disk is non-native."

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

REQUIRED INFO: Capture the output of the CLI commands, dsperr, dsplog

SHM_-4-CD_NATIVE_ERR4

SEVERITY: Error

FORMAT: "slot %d BRAM and Disk non-native. BP Serial #s actual%s, BRAM %s, Disk %s, health0x%x"

FLAG: Stack Trace|Write to Bram

THROTTLING: One Tick

EXPLANATION: "Card Nativity check failed because the BRAM and disk BP serial numbers do not match with each other and with the actual BP Serial Num"

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

REQUIRED INFO: Capture the output of the CLI commands, dsperr, dsplog

SHM_-4-CD_NATIVE_ERR5

SEVERITY: Error

FORMAT: "slot %d Backplane NVRAM read fail and BRAM and Disk non-native. BP Serial #s actual%s, BRAM %s, Disk %s, health0x%x, rebuilding from Disk"

FLAG: Stack Trace|Write to Bram

THROTTLING: One Tick

EXPLANATION: "Backplane NVRAM id could not be read and Card Nativity check failed because the BRAM and disk BP serial numbers match with each other but not with the actual BP Serial Num"

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

REQUIRED INFO: Capture the output of the CLI commands, dsperr, dsplog

SHM_-4-CD_NATIVE_ERR6

SEVERITY: Error

FORMAT: "slot %d BRAM read not Valid. BP Serial #s actual %s, BRAM %s, Disk %s, health0x%x, Rebuilding from Disk"

FLAG: Stack Trace|Write to Bram

THROTTLING: One Tick

EXPLANATION: "Rebuilding databases from Disk as BRAM read is not valid."

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

REQUIRED INFO: Capture the output of the CLI commands, dsperr, dsplog

SHM_-4-CD_NOT_HEALTHY

SEVERITY: Error

FORMAT: "Card not healthy in slot %d. BP Serial #s actual %s, BRAM %s, Disk%s, health0x%x"

FLAG: Stack Trace|Write to Bram

THROTTLING: One Tick

EXPLANATION: "The card is not healthy and hence it is failed."

RECOMMENDED ACTION: Reset the card. If the problem persists copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: 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.

SHM_-2-CD_INSERT

SEVERITY: Major Alert

FORMAT: "SHM INFO Reserved Card inserted at slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The SHM detects a Reserved card insertion"

RECOMMENDED ACTION: "No action required. The slot in which the card is inserted is a RESERVED slot. A slot becomes reserved when there is redundancy added or when user traffic is is configured."

REQUIRED INFO: No Required Info

SHM_-2-PXM_CBC_RDY

SEVERITY: Major Alert

FORMAT: "SHM INFO Peer PXM cell bus card state is Ready for slot %d, Log Count %d, Tick Value %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "tMon detected peer pxm cell bus card state is Ready"

RECOMMENDED ACTION: "No action is required. The peer PXM card is detected in Cbc Ready State"

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.

SHM_-2-PXM_CBC_NOT_RDY

SEVERITY: Major Alert

FORMAT: "SHM INFO Peer PXM cell bus card state is Not Ready for slot %d, Log Count %d, Tick Value %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "tMon detected peer pxm cell bus card state Not Ready"

RECOMMENDED ACTION: "No action is required. The peer PXM card is detected in Cbc Not Ready State"

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.

SHM_-2-PXM_FW_RDY

SEVERITY: Major Alert

FORMAT: "SHM INFO Peer PXM card firmware state is Ready for slot %d, Log Count %d, Tick Value %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "tMon detected peer pxm firmware state ready"

RECOMMENDED ACTION: "No action is required. The peer PXM card is detected in Firmware Ready State"

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.

SHM_-2-PXM_FW_NOT_RDY

SEVERITY: Major Alert

FORMAT: "SHM INFO Peer PXM card firmware state is Not Ready for slot %d, Log Count %d, Tick Value %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "tMon detected peer PXM firmware state Not Ready"

RECOMMENDED ACTION: "No action is required. The peer PXM card is detected in Firmware Not Ready State"

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.

SHM_-7-UNRES_CD_INSERT

SEVERITY: Information

FORMAT: "SHM INFO Unreserved Card inserted at slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The SHM detects an unreserved card insertion"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-INSERT_CD_TYPE

SEVERITY: Information

FORMAT: "SHM INFO Inserted card at slot %d is of type %s (type %d)"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Inserted card type"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-SET_CD_TYPE

SEVERITY: Information

FORMAT: "SHM INFO Inserted card type is set to %s(%d) for slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Inserted card type is being set"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CD_FW_RDY

SEVERITY: Information

FORMAT: "SHM INFO FW READY detected at slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The card has asserted the FW READY bit"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CD_FW_NRDY

SEVERITY: Information

FORMAT: "SHM INFO FW NOT READY detected at slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The card has deasserted the FW READY bit"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-2-CD_REMOVE

SEVERITY: Major Alert

FORMAT: "SHM INFO Reserved Card removed at slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The SHM detects a reserved card removal"

RECOMMENDED ACTION: "No action required. The slot from which the card is removed is a RESERVED slot. A slot becomes reserved when there is redundancy added or when user traffic is is configured."

REQUIRED INFO: No Required Info

SHM_-7-UNRES_CD_REMOVE

SEVERITY: Information

FORMAT: "SHM INFO Unreserved Card removed at slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The SHM detects a card removal"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CD_READY

SEVERITY: Information

FORMAT: "SHM INFO Slot %d, Card %s READY"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The card has transitioned to the ready state"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-DISK_REMOVE

SEVERITY: Information

FORMAT: "SHM INFO %s%d Disk Card removed from Slot %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The disk Card is removed from the slot"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-4-DISK_NOT_SYNCED

SEVERITY: Error

FORMAT: "SHM INFO Slot %d, Card READY (%s), disk not synced"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The card has transitioned to the ready state, but the disk is not yet synced"

RECOMMENDED ACTION: "If the card doesn't transition even after a while, 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.

SHM_-7-DSK_ALRDY_SYNC

SEVERITY: Information

FORMAT: "SHM INFO Disk already sync, disk pslot %d, FUNC %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The disk sync done is called on a disk that is already synced"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-FEATURE_MIS_CLR

SEVERITY: Information

FORMAT: "SHM INFO %s Cleared for pslot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Slot Feature Mismatch Cleared"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-FEATURE_MIS_SET

SEVERITY: Information

FORMAT: "SHM INFO %s for pslot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Slot has Feature Mismatch"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-EXTPOLL_RESP

SEVERITY: Information

FORMAT: "SHM INFO Extended Poll Response received from slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM receives an Extended Poll response"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-IMG_DNLD_START

SEVERITY: Information

FORMAT: "SHM INFO Started Downloading Image to slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM starts downloading image into service module"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-IMG_DNLD_END

SEVERITY: Information

FORMAT: "SHM INFO Image Download is completed to slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM completed downloading image into service module"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-4-INV_CDTYPE

SEVERITY: Error

FORMAT: "SHM ERR Invalid Card type %d for slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM detects an invalid card type"

RECOMMENDED ACTION: "Remove the card and insert the one for which the slot is reserved for"

REQUIRED INFO: No Required Info

SHM_-4-FILE_NOT_FOUND

SEVERITY: Error

FORMAT: "SHM ERR File not found, file %s for slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM cannot find the file"

RECOMMENDED ACTION: "Make sure that the specified file is present in the specified path"

REQUIRED INFO: No Required Info

SHM_-4-CD_NO_RESP

SEVERITY: Error

FORMAT: "ERROR response from %s for remote slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM did not get the response from remote slot"

RECOMMENDED ACTION: "If you see this error more than once then 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.

SHM_-4-MALLOC_FAIL1

SEVERITY: Error

FORMAT: "SHM ERR ssiMalloc Failure, size %d for slot %d, func %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM cannot allocate memory"

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.

SHM_-4-INV_IMG_DESC

SEVERITY: Error

FORMAT: "SHM ERR Image Descriptor validation fail, file %s for slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM cannot validate the image descriptor"

RECOMMENDED ACTION: "Download and reload the image again"

REQUIRED INFO: No Required Info

SHM_-4-INV_IMG_FILE

SEVERITY: Error

FORMAT: "SHM ERR Image checksum validation fail, file %s for slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM checksum validation failed for this image"

RECOMMENDED ACTION: "Download and reload the image again"

REQUIRED INFO: No Required Info

SHM_-4-FILE_POS_ERR

SEVERITY: Error

FORMAT: "SHM ERR the filepos (fseek/lseek) failed for this file, file %s for slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM fseek/lseek failed for this file descriptor"

RECOMMENDED ACTION: "Download and reload the image again"

REQUIRED INFO: No Required Info

SHM_-4-FILE_READ_ERR

SEVERITY: Error

FORMAT: "SHM ERR read operation failed for this file, file %s for slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM read() from file failed for this file descriptor"

RECOMMENDED ACTION: "Download and reload the image again"

REQUIRED INFO: No Required Info

SHM_-4-FILE_STAT_ERR

SEVERITY: Error

FORMAT: "SHM ERR Get info (fstat) operation failed for this file, file %s for slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM fstat() failed for this file descriptor"

RECOMMENDED ACTION: "Download and reload the image again"

REQUIRED INFO: No Required Info

SHM_-7-DSK_C_RBLD_OK

SEVERITY: Information

FORMAT: "SHM INFO SHM RAM Cold Rebuild from Disk is completed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM completed rebuild of its Database from Disk"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-DSK_C_RBLD_ERR

SEVERITY: Information

FORMAT: "SHM INFO: SHM RAM Cold Rebuild from Disk is failed"

FLAG: Write Bram

THROTTLING: One Tick

EXPLANATION: "The SHM failed rebuild of its Database from Disk"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-BRAM_C_RBLD_OK

SEVERITY: Information

FORMAT: "SHM INFO SHM RAM Cold Rebuild from BRAM is completed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM completed rebuild of its Database from BRAM"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-BRAM_C_RBLD_ERR

SEVERITY: Information

FORMAT: "SHM INFO: SHM RAM Cold Rebuild from BRAM is failed"

FLAG: Write Bram

THROTTLING: One Tick

EXPLANATION: "The SHM failed rebuild of its Database from BRAM"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CLRALLCNF_OK

SEVERITY: Information

FORMAT: "SHM INFO SHM RAM, BRAM and Disk Init Rebuild is completed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM completed rebuild of its Database to default value"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CLRALLCNF_ERR

SEVERITY: Information

FORMAT: "SHM INFO: SHM RAM, BRAM and Disk Init Rebuild is Failed"

FLAG: Write Bram

THROTTLING: One Tick

EXPLANATION: "The SHM failed rebuild of its Database to default value"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CLRCNF_OK

SEVERITY: Information

FORMAT: "SHM INFO SHM RAM, BRAM and Disk Partial Rebuild is completed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM completed rebuild of its Database to clrcnf value"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CLRCNF_ERR

SEVERITY: Information

FORMAT: "SHM INFO SHM RAM, BRAM and Disk Partial Rebuild is Failed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM failed rebuild of its Database to clrcnf value"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-RAM_INIT_OK

SEVERITY: Information

FORMAT: "SHM INFO SHM RAM Init Rebuild is completed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM completed rebuild of its Database only in RAM"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-RAM_INIT_ERR

SEVERITY: Information

FORMAT: "SHM INFO SHM RAM Init Rebuild is Failed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM failed rebuild of its Database only in RAM"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CTRL_CD_RBLD

SEVERITY: Information

FORMAT: "SHM INFO BRAM node rstReason %d, cdHealth 0x%x, rstReason %d, rebuildFlag %d"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Info on how the SHM rebuilds its database"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-5-INV_SLOT

SEVERITY: Warning

FORMAT: "%s Invalid slot %d in msg type 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM detects an invalid slot # in a message"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-INV_EXTPOLL_VER

SEVERITY: Information

FORMAT: "SHM INFO Invalid Ext.Poll Resp version from slot %d, FUNC %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SHM receives an Invalid version of Extended Poll response"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-5-INV_API_CALL

SEVERITY: Warning

FORMAT: "%s Unsupported API call message 0x%x from slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM API was called from a slot from which it is not supposed to be called"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-5-OFFLINE_DIAGREQ

SEVERITY: Warning

FORMAT: "%s Offline Diagnosis Request on slot %d %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "A warning message regarding Offline Diagnostics Request"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CD_RESET

SEVERITY: Information

FORMAT: "%s Card in slot %d Reset %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SHM Information that it reset a a card"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-4-SET_CSM_TMR_ERR

SEVERITY: Error

FORMAT: "%s Cannot set timer for slot %d, state %d %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SHM CSM could not set the Timer for the specified slot"

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

REQUIRED INFO: No Required Info

SHM_-5-INV_RST_REASON

SEVERITY: Warning

FORMAT: "SHM ERR Read Invalid Reset Reason from BRAM Slot %d, ResetReason %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The SHM detects Invalid Reset Reason from its Database"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CD_SWFWVERS_CLE

SEVERITY: Information

FORMAT: "SW/FW vers are cleared as %s (%s) in slot %d does not support them"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The SHM clears unnecessary (unsupported) fields from the slotDb for the inserted cardType"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-BC_INFO_CORRECT

SEVERITY: Information

FORMAT: "BC inserted field is being set to TRUE for cardType %s(%d) bay %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SHM corrected BcInserted field in slotDb for the specified card and bay number"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-7-CD_NVIDS_CLEARE

SEVERITY: Information

FORMAT: "NVIDs are cleared as %s (%s) in slot %d does not support them"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "The SHM clears unnecessary (unsupported) fields from the slotDb for the inserted cardType"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

SHM_-5-DB_CORRUPTION

SEVERITY: Warning

FORMAT: "SHM ERR Database Corruption found in %s"

FLAG: No Flag