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

SSI_-3-RAMDEVCREATE

Table Of Contents

SSI_-3-RAMDEVCREATE

SSI_-3-DOSFSINITOPTION

SSI_-7-DEVEXISTS

SSI_-3-DOSFSMKFS

DDTS "ssi"

SSI_-4-INVALID_SPEC

SSI_-4-DEVCREATE_ERROR

SSI_-7-DEVCREATE_OK

DDTS "rpmxf-ssi"

RMI-5-RMIINVALIDPARM

RMI-4-RMIEPIDXINITERR

RMI-4-RMI_IPC_ERR

RMI-5-EPID_IDX_INVALI

RMI-5-RMIINVALIDEPIDX

RMI-5-RMIINVALIDRCVID

RMI-5-RMIRETXACKERR

RMI-5-RMIRETXNACKERR

RMI-5-RMIINVMSGPTR

RMI-4-RMIMSGHDRSPCERR

RMI-5-RMIIPCSNDFAIL

RMI-5-RMITASKNOTOWNER

RMI-4-RMIPORTNOTINIT

RMI-5-RMIPORTINITWARN

RMI-4-RMIPORTDBLINIT

RMI-4-RMIRMTCTXTALLOC

RMI-4-RMIRMTCTXTERROR

RMI-4-RMIINVSESSID

RMI-4-RMIRMTCTXTDELER

RMI-4-RMIRETXQUEUEERR

RMI-4-RMIMSGFREEERR

RMI-5-RMIMSGDUPFAIL

RMI-5-RMIMSGALLOCFAIL

RMI-5-RMIINVMSGHDRPAR

RMI-5-RMIINVLDMSGTYPE

RMI-5-RMIINVRETXPORTI

RMI-5-RMIINVDATAMSGTY

RMI-5-RMIINVALIDEPID

RMI-4-RMIBUFALLOCERR

DDTS "atmsig"

SSIF-5-UNSUPPORTED

SSIF-4-NoTmTable

SSIF-5-BADADDR

SSIF-5-HEAPCREAT

SSIF-5-PAKTYP

SSIF-4-BadTimer

SSIF-4-TickFailed

SSIF-5-DBLFREEERR

DDTS "stats-upload"

STAT-3-FATAL_ERROR

STAT-3-MAJOR_ERROR

STAT-4-ERROR

STAT-5-WARNING

DDTS "stats-upload"

STAT-3-FATAL_ERROR

STAT-4-MAJOR_ERROR

STAT-4-ERROR

STAT-5-WARNING

STAT-7-INFO

DDTS "cema"

STAT-5-LOG

DDTS "legacy-red"

STAT-5-LOG

DDTS "stats-upload"

STAT-5-INVD_DBID

STAT-5-DB_REG

STAT-5-TBL_UPDATE

STAT-5-TBL_GET

STAT-5-INVD_TBLID

STAT-5-INVD_EPID

STAT-5-INVD_INPT

STAT-5-EPID_BIND

STAT-5-REV_CHANGE

STAT-5-REV_CHG_DONE

STAT-5-MESS_HANDLER

STAT-5-INVD_TIMER

STAT-5-TIMER_SET

STAT-4-INVD_FILE_ELEME

STAT-4-INVD_FILE_FORMA

STAT-4-INVD_DEV_LEN

STAT-4-FILE_NOT_FD

STAT-4-SEM_TAKE

STAT-4-INVD_MESS_TYPE

STAT-4-SLOT_NOT_RDY

STAT-4-MESS_SEND

STAT-4-MESS_BUFF

STAT-5-OUT_OF_MEM

STAT-4-SEND_TRAP

STAT-4-ERROR_RES

STAT-4-INVD_ERROR

STAT-4-CWSINDEX_INVD

STAT-4-TRAPFILEOPEN

DDTS "control-point"

SMGR-5-INVD_STATE

SMGR-4-INVD_INPT

SMGR-4-INVD_RET

SMGR-4-INVD_VAL

SMGR-4-INVD_EPID

SMGR-4-HNDL_ATTCH

SMGR-4-RAT_ACK

SMGR-4-WAIT_LOOP

SMGR-5-SEM_CREAT

SMGR-4-INVD_DBID

SMGR-4-INVD_TBID

SMGR-4-DB_REG

SMGR-5-BUF_FREE

SMGR-5-REQ_ABRT

SMGR-4-FILE_DEL

SMGR-5-TRAP_FAIL

SMGR-5-INVD_RET

SMGR-5-INVD_VAL

SMGR-5-INVD_INPT

SMGR-4-INVD_RET

SMGR-4-INVD_VAL

SMGR-5-INVD_FLAG

SMGR-5-INVD_RET

SMGR-5-INVD_VAL

SMGR-5-INVD_REQ

DDTS "stats-upload"

SUPL-5-INVD_INPT

SUPL-4-INVD_RET

SUPL-4-INVD_VAL

SUPL-4-INVD_INPT

SUPL-4-INVD_RET

SUPL-4-INVD_VAL

SUPL-4-INCRT_CALL

DDTS "shm"

SYS_-7-ERR_REPORT_TO_S

SYS_-4-ERR

DIAG-4-ERR

DIAG-7-INFO

DIAG-7-OFFLN_ABORT

DDTS "ssi"

SYS-2-CLRCFG_FAILED

SYS-4-CLRCFG_ERROR

SYS-5-FILECHKSUMERR

SYS-7-STARTUP

SYS-4-STARTUP_ERR1

SYS-4-STARTUP_ERR2

SYS-7-VERSION

SYS-2-CARDINITFAIL

SYS-2-CHASSISFAIL

SYS-3-TASKRECV

SYS-2-RECVTASKFAIL

SYS-3-RUNAWAYTASK

SYS-3-RUNAWYNOSTKTRC

SYS-3-STARVETASK

SYS-3-HANGTASK

SYS-3-HNGNOSTKTRC

SYS-5-IGNRECVACT

SYS-4-FORCESUSPEND

SYS-4-TASKSUSPENDFAIL

SYS-7-RUNTRACETASK

SYS-2-TASKINITFAIL

SYS-1-RTTASKSUSPEND

SYS-1-BKTASKSUSPEND

SYS-6-BKTASKRESTART

SYS-1-TASKLOSTFATAL

SYS-3-TASKLOST

SYS-3-WRONGTYPTKRECV

SYS-1-FILEOPENFAIL

SYS-3-WRNGEVTLOG

SYS-2-PRIADJFAIL

SYS-2-NOFNDPRITSK

SYS-3-BRAMFAIL

SYS-2-EXCEPTION

SYS-4-NOVRAM_1

SYS-4-CHK_CD_TYPE_ERR

SYS-2-NOVRAMFAIL

SYS-7-TEST_DUMP

SYS-7-TEST_STACK

SYS-5-NVRAMCHKSUMERR

SYS-5-SRMBCCHKSUMERR

SYS-7-TEST_DUMPSTK

SYS-7-TEST_BRAM

SYS-7-TIMECHANGE

SYS-7-ZONECHANGE

SYS-4-MSGINVALID

SYS-3-MSGPROCFAIL

SYS-7-LOGMSGCOUNTS

SYS-3-EVENTSAVEFAIL

SYS-7-SAVEFAILCOUNTS

SYS-7-BOOTREGISTERS

SYS-4-NETWORKUPERROR

SYS-4-NETSTANDBYERROR

SYS-4-IPCNFDBERROR

SYS-7-SIG_FILE_MOD

SYS-2-CLRDISK_ERROR1

SYS-4-CLRDISK_ERROR2

SYS-7-CLRDISK_EVENT

SYS-5-INVWRPTR

SYS-5-INVWRPTR2

SYS-7-CHKDSK_INITIATE

SYS-5-CHKDSK_ERROR

SYS-5-CHKDSK_FAILED

SYS-7-CHKDSK_OK

SYS-5-CHKDSK_WARNING

SYS-2-DISK_EJECTOR

SYS-4-DSKUSAGEERR

SYS-7-DSKUSAGEOK

SYS-3-DSKUSAGELOW

SYS-2-DSKUSAGELOWSEV

DDTS "traps"

TRAP-7-TRAPLET_ERR

TRAP-7-IPC_ERR

TRAP-5-INV_ADDR

TRAP-5-ERR_RETURN

TRAP-7-INVALIDINPUT

TRAP-5-PARMOUTOFTRANGE

TRAP-7-PARMINVALID

TRAP-7-PARMINVLENGTH

TRAP-4-FUNCFAIL_STKDUM

TRAP-5-INVALIDNUM

TRAP-5-QUEUEFULL

TRAP-5-INVOIDPTR

TRAP-5-INVPTR

TRAP-5-INVLENGTH

TRAP-5-DATAPTRGET_ERR

DDTS "atmsig"

NETB-5-SSIF_TIMER_INIT

NETB-5-SSIF_TIMER_ENAB

NETB-5-MAIN_EP_INIT_FA

NETB-5-TGM_INIT_FAILED

NETB-5-CLI_INIT_FAILED

NETB-5-EP_INIT_FAILED

NETB-5-UNEXPECTED_TGM_

NETB-5-MEMINIT_ERROR

NETB-5-IPC_MSG_ALLOC_F

NETB-5-IPC_MSG_SEND_FA

DDTS "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

DDTS "traps"

TRAP-4-SEM_FAILED

TRAP-4-SRV_INIT_FAILED

TRAP-5-INVOIDPTR

TRAP-5-INVLENGTH

TRAP-5-INVPTR

DDTS "ccma"

UDP-5-UDP_INIT_ERR

UDP-5-UDP_INTRPT_ERR

UDP-5-UDP_GEN_ERR

UDP-5-UDP_PARAM_ERR

DDTS "vsi"

VSI-5-VSI_MSG_LENGTH

VSI-5-VSI_PG_LENGTH

VSI-5-SYNTAX_ERROR

VSI-5-VSI_CONTROLLER

VSI-5-VSI_SAP

VSI-5-VSI_MSGQ

VSI-5-VSI_SOCKET

VSI-5-VSI_UNKNOWN_CMD

VSI-5-VSIS_TRAP

VSI-7-VSIS_TX

VSI-7-NULL_PTR

VSI-5-MALLOC_FAIL

VSI-5-FREE_FAIL

VSI-5-FBALLOC_FAIL

VSI-5-FBFREE_FAIL

VSI-5-VSI_TIMER

VSI-5-VSI_CLK

VSI-7-SSI_VSI_IF

DDTS "unknown"

VSI-7-E1

VSI-7-VSI_MSG_LENGTH

VSI-7-VSI_PG_LENGTH

VSI-7-VSI_SYNTAX_ERRO

VSI-7-VSI_CONTROLLER

VSI-7-VSI_SAP

VSI-7-VSI_MSGQ

VSI-7-VSI_SOCKET

VSI-7-VSI_UNKNOWN_CMD

VSI-7-VSIS_TRAP

VSI-7-VSIS_TX

VSI-7-NULL_PTR

VSI-7-MALLOC_FAIL

VSI-7-FREE_FAIL

VSI-7-FBALLOC_FAIL

VSI-7-FBFREE_FAIL

VSI-7-VSI_TIMER

VSI-7-VSI_CLK

VSI-7-VSI_ROOT

VSI-7-VSI_PROXY

VSI-7-VSIM_PROXY

DDTS "vsim"

VSIM-5-VSIM_DEBUG

VSIM-7-VSIM_INFO

VSIM-7-VSIM_STATS

VSIM-6-VSIM_NOTICE

DDTS "vsim"

VSIM-5-VSIM_DEBUG

VSIM-7-VSIM_INFO

VSIM-7-VSIM_STATS

VSIM-6-VSIM_NOTICE

DDTS "pxm-connmgm"

VSIS-7-VSIS_MSGQ

VSIS-7-VSIS_PXMCM_MSGP

DDTS "vsi"

VSIS-7-VSIS_MSGQ

DDTS "vsi"

VSIS-7-VSIS_MSGQ

DDTS "vsi"

VSIS-7-VSIS_MSGQ

VSIS-7-INFO_STR

DDTS "pxm-connmgm"

VSIC-5-VSICGENERR

VSIC-5-VSIERRCODE

VSIC-2-VSIMAJORERR

PXMC-4-RAMSYNC

PXMC-4-GENERR

VSIS-5-VSISERR

VSIS-4-NFMAJERR

VSIS-4-GENERR

DDTS "atmsig"

VSM-4-SIGAPIINITERR

VSM-6-SAPIMSGARR

VSM-6-SIGAPIMSGARR

VSM-6-NEWCLIENT

VSM-6-SAPIRESTART

VSM-6-CLIENTSTATECHAN

VSM-6-BULKRESYNC

VSM-6-STATECHANGE

VSM-4-INVCALLREF

VSM-4-SIGAPIERROR

VSM-4-SAPIERROR

VSM-4-WRONGEVENTFORST

VSM-4-DUPRECORDERR

VSM-4-MISSINGRECORD

VSM-4-RECINSERR

VSM-4-RECALLOCERR

VSM-4-NULLPARAMPTR

VSM-7-ADDRSUCC

VSM-4-ADDRERR

VSM-4-UNSUPMSGTYPE

VSM-4-RESOLVERR

VSM-4-IPCMSGERR

VSM-4-INACTIVECLIENT

VSM-4-INVCLIENTID

VSM-4-INVSC

VSM-4-TIMERERROR

VSM-6-CHECKSUM

VSM-6-BULK_RESYNC

VSM-6-SIGAPIMSGSENT

DDTS "pxm-connmgm"

VCNM-4-INIT_FAIL

VCNM-7-UNKNOWN_MSG

VCNM-7-UNKNOWN_TASK

CMM-4-INIT_ERROR_CMM

CMM-5-GET_MSG_ERROR

CMM-4-GET_EVENT_ERROR

CMM-5-UNKNOWN_MSG

CMM-5-RCV_MSG_FAILED

CMM-5-INVALID_SLOT_NO

CMM-7-SLOT_NO_SET

VSM-4-DISK_UPD_FAIL

VSM-4-VSM_UNDO_DEL_BB

VSM-4-VSM_UNDO_MOD_BB

VSM-4-VSM_UNDO_BBIF_F

VSM-7-VSM_BBIF_ADDED

VSM-7-VSM_BBIF_DEL

VSM-7-VSM_BBIF_MOD

VSM-7-VSM_RSC_CNF_CHG

VSM-7-BBCHAN_ADDED

VSM-7-BBCHAN_DELETED

DDTS "unknown"

VCNM-4-INIT_FAIL

VCNM-7-UNKNOWN_MSG

VCNM-7-UNKNOWN_TASK

CMM-4-INIT_ERROR_CMM

CMM-4-GET_MSG_ERROR

CMM-4-GET_EVENT_ERROR

CMM-5-UNKNOWN_MSG

CMM-5-RCV_MSG_FAILED

CMM-5-INVALID_SLOT_NO

CMM-7-SLOT_NO_SET

VSM-4-DISK_UPD_FAIL

VSM-4-VSM_UNDO_DEL_BB

VSM-4-VSM_UNDO_MOD_BB

VSM-4-VSM_UNDO_BBIF_F

VSM-7-VSM_BBIF_ADDED

VSM-7-VSM_BBIF_DEL

VSM-7-VSM_BBIF_MOD

VSM-7-VSM_RSC_CNF_CHG

VSM-7-BBCHAN_ADDED

VSM-7-BBCHAN_DELETED


SSI_-3-RAMDEVCREATE

SEVERITY: Minor Alert
FORMAT: "requested ramdisk name %s, devSize %d, global errno %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to create ramdisk. Services targetted for that device may not be available. Api to create ramdevice failed. All requests involving the ram disk eg. configuration upload, for this slot will fail."
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 Please collect the output of CLIs dspver, dspcds, dsplog, dsperr, dspvers

SSI_-3-DOSFSINITOPTION

SEVERITY: Minor Alert
FORMAT: "ramdisk name %s, global errno %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to create ramdisk because the api to initialize default configuration for dosFs device, failed. All requests involving the ram disk eg. configuration upload, for this slot will fail."
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 Please collect the output of CLIs dspver, dspcds, dsplog, dsperr, dspvers

SSI_-7-DEVEXISTS

SEVERITY: Information
FORMAT: "ramdisk name %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to create ramdisk because a device of the same name already exists."
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 Please collect the output of CLIs dspver, dspcds, dsplog, dsperr, dspvers

SSI_-3-DOSFSMKFS

SEVERITY: Minor Alert
FORMAT: "ramdisk name %s, global errno %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to create ramdisk because the api to initialize the ram device with dosFs, ie dosFsMkfs, failed. All requests involving the ram disk eg. configuration upload, for this slot will fail."
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 Please collect the output of CLIs dspver, dspcds, dsplog, dsperr, dspvers

DDTS "ssi"

SSI_-4-INVALID_SPEC

SEVERITY: Error
FORMAT: "invalid entry\"%d\", in the ramdisk table"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to create ramdisk - invalid spec, targetted service may not be available"
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 Please collect the output of CLIs dspver, dspcds, dsplog, dsperr, dspvers

SSI_-4-DEVCREATE_ERROR

SEVERITY: Error
FORMAT: "appl name \"%s\", ramdisk name \"%s\"."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to create ramdisk, targetted service may not be available"
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 Please collect the output of CLIs dspver, dspcds, dsplog, dsperr, dspvers

SSI_-7-DEVCREATE_OK

SEVERITY: Information
FORMAT: "appl name \"%s\", ramdisk name \"%s\", request size \"%d\", true size \"%d\"."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Created ramdisk"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "rpmxf-ssi"

RMI-5-RMIINVALIDPARM

SEVERITY: Warning
FORMAT: " %s line %d Invalid parameter %s %x (%d)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid EPID from User"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-4-RMIEPIDXINITERR

SEVERITY: Error
FORMAT: " %s, line %d, Epidx Init Error %s Got %x expected %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error while initialization of epid index"
RECOMMENDED ACTION: Copy the error message 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
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-4-RMI_IPC_ERR

SEVERITY: Error
FORMAT: "%d error in IPC operation %s line %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error in low level 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 Please collect the output of CLIs
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-5-EPID_IDX_INVALI

SEVERITY: Warning
FORMAT: "%s invalid EpidIdx %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid EPID Index from User"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-5-RMIINVALIDEPIDX

SEVERITY: Warning
FORMAT: "%s line %d Invalid Epidx %d, endPointPtr %x, index %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

RMI-5-RMIINVALIDRCVID

SEVERITY: Warning
FORMAT: "%s line %d Invalid RcvId (%x-%x-%d) on Epid %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

RMI-5-RMIRETXACKERR

SEVERITY: Warning
FORMAT: "%s, line %d, Error %s Epid %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

RMI-5-RMIRETXNACKERR

SEVERITY: Warning
FORMAT: "%s, line %d, Error %s Epid %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

RMI-5-RMIINVMSGPTR

SEVERITY: Warning
FORMAT: "%s, line %d, Invalid Msg Ptr, msgType %d, Epid %x, Port %d, SeqNum %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid message pointer was passed into the function. This is an internal software error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-4-RMIMSGHDRSPCERR

SEVERITY: Error
FORMAT: "%s, line %d, No space for MsgHdr, msgType %d, Epid %x, Port %d, SeqNum %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error not enough space in msg to insert RMI msg header"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of CLIs
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-5-RMIIPCSNDFAIL

SEVERITY: Warning
FORMAT: "%s, line %d, Error %x sending msgType %d, Epid %x, Port %d, SeqNum %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The specified IPC error occurred while sending the specified message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-5-RMITASKNOTOWNER

SEVERITY: Warning
FORMAT: "%s, line %d Non-owner task %x attempting to use Epidx %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A non-owner task is trying to operate on the specified Epidx. This is an internal software error."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-4-RMIPORTNOTINIT

SEVERITY: Error
FORMAT: "%s, line %d Port %d not initialized on Epidx %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error RMI port 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 Please collect the output of CLIs
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-5-RMIPORTINITWARN

SEVERITY: Warning
FORMAT: "%s, line %d Port %d not initialized on Epidx %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Attempted operation on an RMI port that is not initialized"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-4-RMIPORTDBLINIT

SEVERITY: Error
FORMAT: "%s, line %d Port %d already initialized on Epidx %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error initialization of a port that is already 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 Please collect the output of CLIs
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-4-RMIRMTCTXTALLOC

SEVERITY: Error
FORMAT: "%s, line %d Error %s on Epidx %d, Port %d, rmtEpid %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error while allocating memory for a new 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 Please collect the output of CLIs
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-4-RMIRMTCTXTERROR

SEVERITY: Error
FORMAT: "%s, line %d Error %s on Epidx %d, Port %d, rmtEpid %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error while accessing the 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 Please collect the output of CLIs
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-4-RMIINVSESSID

SEVERITY: Error
FORMAT: "%s <invSessionId> e%d,p%d,es%d,rs%d,m%d,h%d,t%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An RMI message was received using an invalid session 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
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-4-RMIRMTCTXTDELER

SEVERITY: Error
FORMAT: "%s, line %d Error %s on Epidx %d, Port %d, rmtEpid %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error while trying to delete 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 Please collect the output of CLIs
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-4-RMIRETXQUEUEERR

SEVERITY: Error
FORMAT: "%s, line %d, operation %s error %x on Epidx %d Retransmission Q"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI internal error while 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 Please collect the output of CLIs
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-4-RMIMSGFREEERR

SEVERITY: Error
FORMAT: "Error %x freeing an RMI message"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI memory error while freeing an RMI 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
1. dspcds, dsprevs
2. dsplog -mod RMI
3. dsplog -mod FIPC

RMI-5-RMIMSGDUPFAIL

SEVERITY: Warning
FORMAT: "%s, line %d, Message dup failed, error %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

RMI-5-RMIMSGALLOCFAIL

SEVERITY: Warning
FORMAT: "%s, line %d, Message dupallocation failed, error %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

RMI-5-RMIINVMSGHDRPAR

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

RMI-5-RMIINVLDMSGTYPE

SEVERITY: Warning
FORMAT: "%s, line %d, Invalid message type %d, Epidx %d, Port %d, srcEpid %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

RMI-5-RMIINVRETXPORTI

SEVERITY: Warning
FORMAT: "%s, line %d, portId %d, srcSlot %d "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Message had invalid Retransmission Rmi PortID"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-5-RMIINVDATAMSGTY

SEVERITY: Warning
FORMAT: "%s, line %d, Invalid message type %d, Port %d, srcSlot %d "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Incoming data message type is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-5-RMIINVALIDEPID

SEVERITY: Warning
FORMAT: "%s, line %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI endpoint ID is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RMI-4-RMIBUFALLOCERR

SEVERITY: Error
FORMAT: "Error in buffer allocation errno %x Task %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "RMI memory error while allocating buffer for RMI 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
2. dsplog -mod RMI
3. dsplog -mod FIPC

DDTS "atmsig"

SSIF-5-UNSUPPORTED

SEVERITY: Warning
FORMAT: "Unsupported or unimplemented feature %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: " feature is not supported"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

SSIF-4-NoTmTable

SEVERITY: Error
FORMAT: "TaskID 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSIF timer table full or no such entry for the expected task"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

SSIF-5-BADADDR

SEVERITY: Warning
FORMAT: "Error in %s addr=0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Internal error, address is out of range"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

SSIF-5-HEAPCREAT

SEVERITY: Warning
FORMAT: "%s mem=0x%X len=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssif failed to create heap"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

SSIF-5-PAKTYP

SEVERITY: Warning
FORMAT: "Paktype conversion error in %s = (0x%x, %d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Paktype conversion error"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

SSIF-4-BadTimer

SEVERITY: Error
FORMAT: "%s typ=%d, key/ctx=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssif can not get timer infomation"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

SSIF-4-TickFailed

SEVERITY: Error
FORMAT: "%s %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssif fail to arm the timer"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

SSIF-5-DBLFREEERR

SEVERITY: Warning
FORMAT: "Double free error in %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssif try to free mblk which is already freed"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

DDTS "stats-upload"

STAT-3-FATAL_ERROR

SEVERITY: Minor Alert
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Fatal Error in Common Part of Stat Module"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-3-MAJOR_ERROR

SEVERITY: Minor Alert
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Major Error in Common Part of Stat Module"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Minor Error in Common Part of Stat Module, such as Invalid parameter Null stat element found in queue Failed to unlock a file and more ..."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-WARNING

SEVERITY: Warning
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Warning in Common Part of Stat Module, such as Attempt to unlock a file failed Can not remove a supplied file name "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "stats-upload"

STAT-3-FATAL_ERROR

SEVERITY: Minor Alert
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Fatal Error in SFM API"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-MAJOR_ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Major Error in SFM API. Here are some of the possible error Invalid parameter File name supplied are longer than the maximum length defined Unable to change directory and more ..."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4
s

STAT-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Minor Error in SFM API. Here are the possible error Incorrect card state Can not release semaphore Can not open stat device Invalid parameter and more ... "
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-WARNING

SEVERITY: Warning
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Warning in SFM API. Here are the possible warning Can not take semaphore Allocate IPC buffer failed IPC message send failed and more ..."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

STAT-7-INFO

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "Information in SFM API."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "cema"

STAT-5-LOG

SEVERITY: Warning
FORMAT: "STAT line %d error code %ld; %ld %ld\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "If the error number is 40961 - Info message. 40962 - This is an unused error value. Please ignore. 40963 - This is an unused error value. Please ignore. 40964 - This is an unused error value. Please ignore. 40965 - This message says that there was an internal software error while opening a file to create the stats file. The stats file generated at this instant may not be available. 40966 - This message says that there was an internal software error while writing a file to create the stats file. The stats file generated at this instant may not be available. 40967 - This message says that there was an internal software error while closing a file to create the stats file. The stats file generated at this instant may not be available. 40968 - Card statistics collection has failed. 40969 - Line statistics collection has failed. 40970 - Device driver error. 40971, 40972, 40973, 40974 & 40975 - Hardware error. Stats collection could not be done. 40976, 40977, 40978, 40979, 40980, 40981, 40982,
RECOMMENDED ACTION: "If the error number is 40961 - No action is needed. 40962 - No action is needed. 40963 - No action is needed. 40964 - No action is needed. 40965 - Please collect the following info. Contact TAC 40966 - Please collect the following info. Contact TAC 40967 - Please collect the following info. Contact TAC 40968 - Please collect the following info. Contact TAC 40969 - Please collect the following info. Contact TAC 40970 - Please collect the following info. Contact TAC 40971, 40972, 40973, 40974 & 40975 - Please collect the following info and contact Cisco Technical Support. 40976, 40977, 40978, 40979, 40980, 40981, 40982,
REQUIRED INFO "If the error number is 40961 - No info need to be taken. 40962 - No action is needed. 40963 - No action is needed. 40964 - No action is needed. 40965 - On PXM45
1. dspdate
2. dsplog -sl <slot that experienced this error>
3. dspcd <slot that experienced err>
On AXSM
1. sfmdbshow 4
40966 - On PXM45
1. dspdate
2. dsplog -sl <slot that experienced this error>
3. dspcd <slot that experienced err>
On AXSM
1. sfmdbshow 4
40967 - On PXM45
1. dspdate
2. dsplog -sl <slot that experienced this error>
3. dspcd <slot that experienced err>
On AXSM
1. sfmdbshow 4
40968 - On PXM45
1. dspdate
2. dsplog -sl <slot that experienced this error>
3. dspcd <slot that experienced err>
40969 - On PXM45
1. dspdate
2. dsplog -sl <slot that experienced this error>
3. dspcd <slot that experienced err>
40970 - On PXM45
1. dspdate
2. dsplog -sl <slot that experienced this error>
3. dspcd <slot that experienced err>
40971, 40972, 40973, 40974 & 40975 - On PXM45
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
40976, 40977, 40978, 40979, 40980, 40981, 40982,
40983, 40984 -
On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
40992, 40993, 40994, 40995 - On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
41008 - On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
41009 - ...
41024, 41025, 41026, 41027 - On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
41028 - On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
41029 - On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
41030 - On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
41031 - On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
41032 - On PXM45 :
1. dspdate
2. dsplog -sl <slot that experienced this err>
3. dspcd <slot that experienced err>
4. dsperr <slot that experienced err>
"

DDTS "legacy-red"

STAT-5-LOG

SEVERITY: Warning
FORMAT: "STAT error %s %d %ld %ld %ld\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "stats-upload"

STAT-5-INVD_DBID

SEVERITY: Warning
FORMAT: "STATUPLD DBID %s, cannot be created, Errno 0x%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to Create DiskDB."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-DB_REG

SEVERITY: Warning
FORMAT: "STATUPLD DB Reg %s, cannot register, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to Register the DiskDB."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-TBL_UPDATE

SEVERITY: Warning
FORMAT: "STATUPLD TBL NAME %s, cannot update table, Errno 0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to initialize the DiskDB."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-TBL_GET

SEVERITY: Warning
FORMAT: "STATUPLD TBL NAME %s, get failed, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to perform get on table."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

STAT-5-INVD_TBLID

SEVERITY: Warning
FORMAT: "STATUPLD TBLID %s, cannot be created, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to Create Table in DiskDB."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-INVD_EPID

SEVERITY: Warning
FORMAT: "STATUPLD EPID %s, cannot be created, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to Create EPID"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-INVD_INPT

SEVERITY: Warning
FORMAT: "STATUPLD Input input %s invalid %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid input to function"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

STAT-5-EPID_BIND

SEVERITY: Warning
FORMAT: "STATUPLD Binding %s, cannot be created, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to bind EPID"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-REV_CHANGE

SEVERITY: Warning
FORMAT: "STATUPLD TBL Rev change %s, cannot be registered, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to register Disk DB table revision change."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

STAT-5-REV_CHG_DONE

SEVERITY: Warning
FORMAT: "STATUPLD TBL Rev change done %s, cannot be registered, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to commit Disk DB table revision change."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

STAT-5-MESS_HANDLER

SEVERITY: Warning
FORMAT: "STATUPLD MESSAGE HANDLER %s cannot be attached, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Fail to Attach IPC Message Handler."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-INVD_TIMER

SEVERITY: Warning
FORMAT: "STATUPLD TIMER %s cannot be created, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Fail to Create Timer"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

STAT-5-TIMER_SET

SEVERITY: Warning
FORMAT: "STATUPLD TIMER %s cannot be set, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Fail to Set the Timer"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

STAT-4-INVD_FILE_ELEME

SEVERITY: Error
FORMAT: "SUM Invalid File Element from lSlot %d, Errno 0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Received Invalid File Element."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-INVD_FILE_FORMA

SEVERITY: Error
FORMAT: "STATUPLD FILENAME %s has invalid format, Errno 0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Received an Invalid Format File."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-INVD_DEV_LEN

SEVERITY: Error
FORMAT: "STATUPLD DEVICE %d char is not enough, Errno 0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Device Length is not Big enough."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-FILE_NOT_FD

SEVERITY: Error
FORMAT: "STATUPLD FILE %s is not found, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Cannot Find the Specified File."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-SEM_TAKE

SEVERITY: Error
FORMAT: "STATUPLD SEM Semaphore cannot be taken in %s, Errno 0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Semaphore Cannot be Taken."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-INVD_MESS_TYPE

SEVERITY: Error
FORMAT: "STATUPLD MESSAGE %s Receives an Invalid IPC Message, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Received Invalid IPC Message"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-SLOT_NOT_RDY

SEVERITY: Error
FORMAT: "STATUPLD SLOT Slot %d is not Registered, Errno 0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Slot is not Register and Initialized"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-MESS_SEND

SEVERITY: Error
FORMAT: "STATUPLD MESS SEND %s message cannot be sent, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Cannot Send Message."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-MESS_BUFF

SEVERITY: Error
FORMAT: "STATUPLD MESS BUFFER %s message cannot be sent, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Cannot Allocate Message Buffer."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-5-OUT_OF_MEM

SEVERITY: Warning
FORMAT: "SUM Cannot Allocate Memory Struct in %s, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Fail to Allocate Memory."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-SEND_TRAP

SEVERITY: Error
FORMAT: "SUM Cannot Send Out %s Trap, Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Fail to Send Trap."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-ERROR_RES

SEVERITY: Error
FORMAT: "SUM %s Message Received with %d in resMsg, setting Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Response Message Contains Error."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-INVD_ERROR

SEVERITY: Error
FORMAT: "SUM %s has received invalid error message (%d), setting Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Error Message."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-CWSINDEX_INVD

SEVERITY: Error
FORMAT: "k_statUpld %d - Invalid cwsConfIndex in %s, setting Errno 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid cwsConfIndex value"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

STAT-4-TRAPFILEOPEN

SEVERITY: Error
FORMAT: "SUM Cannot open %s for trap file."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Trap File Open Error."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any statistics file upload from broadband service modules. The message logged in system log identifies the nature of software error. It also contains a unique error number. Both these are useful for analyzing the root cause. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of the following CLIs On the controller card (a) dspcds (b) dspver (c) dsplog (d) sumdbshow On the Service Module card (a) dspcd (b) dspver (c) sfmdbshow 4

DDTS "control-point"

SMGR-5-INVD_STATE

SEVERITY : Warning
FORMAT : "%s: %s"
FLAG : No Flag
THROTTLING : One Tick
EXPLANATION : "Invalid Controller Card State for enabling statistics."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO : Please collect the output of CLIs: dspver, dspcds, dsplog

SMGR-4-INVD_INPT

SEVERITY: Error
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid input to function."
RECOMMENDED ACTION:
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-INVD_RET

SEVERITY: Error
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Return code from function."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-INVD_VAL

SEVERITY: Error
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Value."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-INVD_EPID

SEVERITY: Error
FORMAT: "%s EPID cannot be created"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to Create EPID"
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 information using the following CLIs dspcds, dspver, dsplog, dsperr "

SMGR-4-HNDL_ATTCH

SEVERITY: Error
FORMAT: "%s Failed to attatch Handler"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to bind EPID to a handler"
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-RAT_ACK

SEVERITY: Error
FORMAT: "%s Failed to ack Statistics Enable RAT after initialization"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to Ack RAT"
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-WAIT_LOOP

SEVERITY: Error
FORMAT: "%s Exited from ssiIpcComEpWait loop"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Possible SSI ERROR"
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-5-SEM_CREAT

SEVERITY: Warning
FORMAT: "%s Semaphore cannot be created, SEM NAME = %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Semaphore Cannot be Created."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-INVD_DBID

SEVERITY: Error
FORMAT: "%s %s, cannot be created"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to Create DiskDB."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-INVD_TBID

SEVERITY: Error
FORMAT: "%s %s, cannot be created"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to Create Disk DB Table."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-DB_REG

SEVERITY: Error
FORMAT: "%s %s, cannot be registered"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to register Disk DB."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-5-BUF_FREE

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to free buffer"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SMGR-5-REQ_ABRT

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SNMP Request aborted."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SMGR-4-FILE_DEL

SEVERITY: Error
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Deletion of statistics enable file from disk failed."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-5-TRAP_FAIL

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failure to send trap to the Network Manager."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SMGR-5-INVD_RET

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid return value."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SMGR-5-INVD_VAL

SEVERITY: Warning
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Value."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SMGR-5-INVD_INPT

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid input to API."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-INVD_RET

SEVERITY: Error
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Invalid Return code."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-4-INVD_VAL

SEVERITY: Error
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Value."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-5-INVD_FLAG

SEVERITY: Warning
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Enable info is kept in DB and RAM. The flag indicating its validity is FALSE i.e info on RAM is invalid ."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-5-INVD_RET

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Invalid Return code."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-5-INVD_VAL

SEVERITY: Warning
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Value."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SMGR-5-INVD_REQ

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid request."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for enabling statistics. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

DDTS "stats-upload"

SUPL-5-INVD_INPT

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid input."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for uploading the statistics file constructed by putting together the files from all narrow band service modules on the shelf. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SUPL-4-INVD_RET

SEVERITY: Error
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Invalid 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 Please collect the output of CLIs dspver, dspcds, dsplog

SUPL-4-INVD_VAL

SEVERITY: Error
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Value."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for uploading the statistics file constructed by putting together the files from all narrow band service modules on the shelf. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SUPL-4-INVD_INPT

SEVERITY: Error
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid input."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for uploading the statistics file constructed by putting together the files from all narrow band service modules on the shelf. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SUPL-4-INVD_RET

SEVERITY: Error
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Invalid Return code."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for uploading the statistics file constructed by putting together the files from all narrow band service modules on the shelf. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SUPL-4-INVD_VAL

SEVERITY: Error
FORMAT: "%s %s %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Value."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for uploading the statistics file constructed by putting together the files from all narrow band service modules on the shelf. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SUPL-4-INCRT_CALL

SEVERITY: Error
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Incorrect call to routine."
RECOMMENDED ACTION: This error identifies the cause of rejecting the request for uploading the statistics file constructed by putting together the files from all narrow band service modules on the shelf. Each error contains a error message. Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information for further analysis.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

DDTS "shm"

SYS_-7-ERR_REPORT_TO_S

SEVERITY : Information
FORMAT : "%s non-fatal major alarm to shelf manager"
FLAG : No Flag
THROTTLING : One Tick
EXPLANATION : "Not all errors are reported to SHM. This log tells what was reported and what skipped."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : No Required Info

SYS_-4-ERR

SEVERITY: Error
FORMAT: "SYSDIAG %s, %d, 0x%x, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The System Diagnostics task encountered an internal error."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

DIAG-4-ERR

SEVERITY: Error
FORMAT: "DIAG slot %d, error = 0x%08x %s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Diagnostics encountered an 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 No Required Info

DIAG-7-INFO

SEVERITY: Information
FORMAT: "DIAG slot %d, status = PASS (%d) %s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Offline diagnostic test completed successfully."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

DIAG-7-OFFLN_ABORT

SEVERITY: Information
FORMAT: "Offline diag terminated at slot %d. Reason %s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Offline diag was terminated due to user abort or sys diag timeout"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "ssi"

SYS-2-CLRCFG_FAILED

SEVERITY : Major Alert
FORMAT : "%s"
FLAG : Write Bram
THROTTLING : One Tick
EXPLANATION : "Previously entered CLI command clrcnf/clrallcnf didn't go thru properly and hence there might be residual databases left on the node"
RECOMMENDED ACTION: "Try clrcnf/clrallcnf again and if the same problem persists, contact Cisco TAC"
REQUIRED INFO : Capture the output of the CLI commands, dsperr, dsplog and collect the coredump file if a coredump occurred.

SYS-4-CLRCFG_ERROR

SEVERITY : Error
FORMAT : "%s"
FLAG : Write Bram
THROTTLING : One Tick
EXPLANATION : "Configuration files, directories specified in the event could not be deleted in response to clrallcnf/clrcnf which could be due to a file system error. However these files, directories were succesfully renamed so the configuration has been deleted. Examine these directories and file system."
RECOMMENDED ACTION: "Try to remove the file(s) manually, if they are not getting deleted contact Cisco TAC"
REQUIRED INFO : Capture the output of the CLI commands, dsperr, dsplog and collect the coredump file if a coredump occurred.

SYS-5-FILECHKSUMERR

SEVERITY : Warning
FORMAT : "Checksum Err: %s %x, %x"
FLAG : No Flag
THROTTLING : One Tick
EXPLANATION : "The runtime or boot file file encountered a checksum error"
RECOMMENDED ACTION: "The runtime or boot file may be corrupted. FTP the right image on the node & try the loadrev/setrev/burnboot command again "
REQUIRED INFO : "Please capture the foll information : dsplog dspcds dsprevs -s ll C:/FW "

SYS-7-STARTUP

SEVERITY: Information
FORMAT: "System is up, Reset Reason [%s]"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "System started after an expected reset due to manual intervention."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-4-STARTUP_ERR1

SEVERITY: Error
FORMAT: "System is up, Reset Reason [%s]"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "System started after a reset due to a failure as specified by the Reset Reason."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, and collect the coredump (if any) done by the card and 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 and collect the coredump file if a coredump occurred.

SYS-4-STARTUP_ERR2

SEVERITY: Error
FORMAT: "System is up, Reset Reason [%s], Reset Type [%s]"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "System started after a reset due to a failure as specified by the Reset Reason and Reset Type."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, and collect the coredump (if any) done by the card and 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 and collect the coredump file if a coredump occurred.

SYS-7-VERSION

SEVERITY: Information
FORMAT: "Boot Code Rev [%s], FW Rev [%s]"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "Version of Backup Boot and runtime FW image."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-2-CARDINITFAIL

SEVERITY: Major Alert
FORMAT: "Card initialization failed during %s. Rc=%d Errno=%x."
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "Card Initialization failed in the specified 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 No Required Info

SYS-2-CHASSISFAIL

SEVERITY: Major Alert
FORMAT: "Chassis error errmsg %s, rc=%d, errno=%x."
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "Chassis error in the specified 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 No Required Info

SYS-3-TASKRECV

SEVERITY: Minor Alert
FORMAT: "Task %p[%s] Recovery %s action is %s."
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "A task has disappeared or suspended."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-2-RECVTASKFAIL

SEVERITY: Major Alert
FORMAT: "Task %p[%s] Recovery failed to %s."
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "A task has disappeared or suspended, and SYSTEM is not RESET"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-RUNAWAYTASK

SEVERITY: Minor Alert
FORMAT: "Task %p[%s] is running away on CPU - %s task."
FLAG: Write to Bram | Dump Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The system has a task that may be in an infinite loop."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-RUNAWYNOSTKTRC

SEVERITY: Minor Alert
FORMAT: "Task %p[%s] is running away on CPU - %s task."
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The system has a task that may be in an infinite loop. This event is same as RUNAWAYTASK except that trace is not dumped because the the semaphore that is necessary to dump the trace is not available."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-STARVETASK

SEVERITY: Minor Alert
FORMAT: "Task %p[%s] has not been able to get CPU for %d minutes."
FLAG: Write to Bram | Dump Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The system has a task that is not getting any CPU time."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-HANGTASK

SEVERITY: Minor Alert
FORMAT: "Task %p[%s] has been %s at %p for %d minutes."
FLAG: Write to Bram | Run Log Function
THROTTLING One Tick
EXPLANATION: "The system has a task that is hung on the specified object for the specified time."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-HNGNOSTKTRC

SEVERITY: Minor Alert
FORMAT: "Task %p[%s] has been %s at %p for %d minutes."
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The system has a task that is hung on the specified object for the specified time. This event is same as HANGTASK except that trace is not dumped because the the semaphore that is necessary to dump the trace is not available."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-5-IGNRECVACT

SEVERITY: Warning
FORMAT: "Task %s is %sIgnored"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The Task Monitor detected specified problem with the specified task. But, the recovery actions are disabled. So, Task Mitor has ignored it."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-4-FORCESUSPEND

SEVERITY: Error
FORMAT: "Task %p[%s] is suspended forcebly."
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The specified task is running away and is suspend safe as it would have been holding one or more mutex semaphores. This task was suspended forceably by the Task Monitor."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SYS-4-TASKSUSPENDFAIL

SEVERITY: Error
FORMAT: "Suspend of task %p for SSI_TID %p failed. Errno=0x%x"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The suspension of VxWorks task used to implement the SSI_TID failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SYS-7-RUNTRACETASK

SEVERITY: Information
FORMAT: "Trace dump"
FLAG: Run Log Function
THROTTLING One Tick
EXPLANATION: "Dumps the contents of the full buffer."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-2-TASKINITFAIL

SEVERITY: Major Alert
FORMAT: "Task[%s] failed of spawning"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "Failed to spawn 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 No Required Info

SYS-1-RTTASKSUSPEND

SEVERITY: Fatal
FORMAT: "Root Task is suspended due to task spawn NAK/timeout"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The Root Task is suspended, because of a NAK or timeout trying to spawn the static tasks."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-1-BKTASKSUSPEND

SEVERITY: Fatal
FORMAT: "Background Task is suspended and could not restart"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The Background Task is suspended, and could not restart."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-6-BKTASKRESTART

SEVERITY: Notice
FORMAT: "Background Task is suspended and restart is successful"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The Background Task got suspended, and restart is successful."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-1-TASKLOSTFATAL

SEVERITY: Fatal
FORMAT: "Trouble-Task[%s] action is SYSTEM RESET"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "A task has disappeared or suspended, and could cause system RESET"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-TASKLOST

SEVERITY: Minor Alert
FORMAT: "Trouble-Task[%s] action is %s"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "A task has disappeared or suspended."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-WRONGTYPTKRECV

SEVERITY: Minor Alert
FORMAT: "Wrong Type[%d] to recv task[%s}"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "taskRecover() wrong type to recover a 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 No Required Info

SYS-1-FILEOPENFAIL

SEVERITY: Fatal
FORMAT: "failed to open event log file"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to open event log file."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-WRNGEVTLOG

SEVERITY: Minor Alert
FORMAT: "Error Task receives a message other than ERR_LOG_MSG"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error Task has received a message other than the message type of ERR_LOG_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 No Required Info

SYS-2-PRIADJFAIL

SEVERITY: Major Alert
FORMAT: "Failed to adjust the priority, Task[%s}, TaskId[%d]"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to adjust the priority for a 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 No Required Info

SYS-2-NOFNDPRITSK

SEVERITY: Major Alert
FORMAT: "Failure to find the highest priority ready task"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failure to find the highest priority ready task in trGet()."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-3-BRAMFAIL

SEVERITY: Minor Alert
FORMAT: "BRAM checksum failed %ud, %ud"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "BRAM checksum 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 No Required Info

SYS-2-EXCEPTION

SEVERITY: Major Alert
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Exceptional Interrupt occurred."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-4-NOVRAM_1

SEVERITY: Error
FORMAT: "Function %s failed. Cardtype %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid card 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 No Required Info

SYS-4-CHK_CD_TYPE_ERR

SEVERITY: Error
FORMAT: "Function %s failed. %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Function chkCardType returned 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 No Required Info

SYS-2-NOVRAMFAIL

SEVERITY: Major Alert
FORMAT: "Novram on %s has checksum failure %ud, %ud"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "BRAM checksum 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 No Required Info

SYS-7-TEST_DUMP

SEVERITY: Information
FORMAT: "%s"
FLAG: Dump Trace
THROTTLING One Tick
EXPLANATION: "Test for Dump Trace."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-TEST_STACK

SEVERITY: Information
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Test for Stack Trace."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-5-NVRAMCHKSUMERR

SEVERITY: Warning
FORMAT: "For %s. Calculated = %u, received = %u"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "NVRAM Read failed because of Checksum error "
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-5-SRMBCCHKSUMERR

SEVERITY: Warning
FORMAT: "For %s. Calculated = %u, received = %u"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "SRM BC NVRAM had a checksum error "
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-TEST_DUMPSTK

SEVERITY: Information
FORMAT: "%s"
FLAG: Stack Trace|Dump Trace
THROTTLING One Tick
EXPLANATION: "Test for Stack Trace and Dump Trace."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-TEST_BRAM

SEVERITY: Information
FORMAT: "%s"
FLAG: Write to Bram|Stack Trace|Dump Trace
THROTTLING One Tick
EXPLANATION: "Test for Bram and Stack Trace and Dump Trace."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-TIMECHANGE

SEVERITY: Information
FORMAT: "Time changed - Old Date/Time %02d/%02d/%04d %02d%02d%02d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This information event indicates that the date or time for the shelf has been updated. The new time is the timestamp on the event while the old time is given in the message."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-ZONECHANGE

SEVERITY: Information
FORMAT: "Time zone changed - New %s(Offset %d) Old %s(Offset %d)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This information event indicates that the time zone information for the shelf has been updated. The new and old time zone information is given in the message."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-4-MSGINVALID

SEVERITY: Error
FORMAT: "Received invalid msg to %s. Size=%d Msg=%08x %08x %08x %08x %08x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The message received by the specified function as a parameter is invalid. The message size and contexts are specified."
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

SYS-3-MSGPROCFAIL

SEVERITY: Minor Alert
FORMAT: "Processing log messages failed %d consecutive times. errno=%x"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The processing of log messages failed the specified number of consecutive times. There is a problem with the received messages or the receiving message queue. The last time failed with the specified error number."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-7-LOGMSGCOUNTS

SEVERITY: Information
FORMAT: "Log Message Counts Evts %d Errs %d Inv %d EvtSave %d ErrSave %d"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The following counts were accumulated for processing of log messages. The first count is the number of event messages processed. The second count is the number of error messages processed. The third count is the number of invalid messages received. The fourth count is the number of times event save has failed. The fifth count is the number of times error saving has failed."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-3-EVENTSAVEFAIL

SEVERITY: Minor Alert
FORMAT: "Saving events to disk failed %d consecutive times. errno=%x"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The saving of events to disk failed the specified number of consecutive times. There is a problem with saving the events to disk. The last time failed with the specified error number."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SYS-7-SAVEFAILCOUNTS

SEVERITY: Information
FORMAT: "Save Fail Counts Total %d Open %d Creat %d Seek %d Write %d Flush %d"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The following counts were accumulated for saving events to disk. The first count is the total number of saves that failed. The second count is the number of event file opens that failed. The third count is the number of event file creates that failed. The fourth count is the number of event file seeks that failed. The fifth count is the number of event file writes that failed. And the sixth count is the number of event file flushes that failed."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-BOOTREGISTERS

SEVERITY: Information
FORMAT: "Boot ResetType=0x%x ResetReason=0x%x ResetPc=0x%x StatusReg=0x%x CauseReg=0x%x CacheErr=0x%x"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The values of the registers whenever a boot of the card happens. This gives detailed information what the state of the CPU was when the reset occurred."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-4-NETWORKUPERROR

SEVERITY: Error
FORMAT: "Unable to activate %s interface. %s failed(errno=%x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The specified network interface failed to activate for the reason specified. It failed with the specified error number. This error could be due an incorrect ip configuration for the specified interface."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-4-NETSTANDBYERROR

SEVERITY: Error
FORMAT: "Unable to start standby ethernet interface. %s failed(errno=%x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The standby ethernet network interface failed to activate for the reason specified. It failed with the specified error number. This error could be due an incorrect ip configuration for the bootChange ethernet values."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-4-IPCNFDBERROR

SEVERITY: Error
FORMAT: "Ip Config Db Error. %s failed in %s. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The Ip configuration ram database had the specified database error in the function specified. It failed with the specified error number."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-SIG_FILE_MOD

SEVERITY: Information
FORMAT: "Signature file %s successfully %s"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The nativity signature file is created/deleted"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-2-CLRDISK_ERROR1

SEVERITY: Major Alert
FORMAT: "Line# %d, Failed to delete or rename nativity signature file %s, DELETE it manually"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "SHM failed to delete or rename the nativity signature file, DELETE it manually"
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

SYS-4-CLRDISK_ERROR2

SEVERITY: Error
FORMAT: "Line# %d, Renamed the nativity signature file %s to %s, DELETE it manually"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "SHM failed to delete the nativity signature file and so renamed it to the specified file, DELETE it manually"
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

SYS-7-CLRDISK_EVENT

SEVERITY: Information
FORMAT: "Line %d - %s"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "Events reported by/in the sysClrDsk function"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-5-INVWRPTR

SEVERITY: Warning
FORMAT: "Invalid write pointer. %s=%p"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The specified address is not a valid address to write to."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-5-INVWRPTR2

SEVERITY: Warning
FORMAT: "Invalid write pointer. %s=%p, %s=%p"
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "The specified address is not a valid address to write to."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-CHKDSK_INITIATE

SEVERITY: Information
FORMAT: "Chkdsk initiated for device %s"
FLAG: Write to Bram
THROTTLING No Throttling
EXPLANATION: "Chkdsk initiated for the specified device"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-5-CHKDSK_ERROR

SEVERITY: Warning
FORMAT: "%s,Device=%s,errno=%d"
FLAG: Write to Bram
THROTTLING No Throttling
EXPLANATION: "ChkDsk reported and error due to the specified reason on the device for which it was doing a chkdsk"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-5-CHKDSK_FAILED

SEVERITY: Warning
FORMAT: "ChkDsk failed device %s,errno= %d
FLAG: Write to Bram
THROTTLING No Throttling
EXPLANATION: "ChkDsk failed for the specific device"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-CHKDSK_OK

SEVERITY: Information
FORMAT: "%s,path=%s,arg1=%d,arg2=%d,arg3=%d,arg4=%d"
FLAG: Write to Bram
THROTTLING No Throttling
EXPLANATION: "ChkDsk successful for the specific path"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-5-CHKDSK_WARNING

SEVERITY: Warning
FORMAT: "%s,Path=%s,arg1=%d,arg2=%d,arg3=%d,arg4=%d"
FLAG: Write to Bram
THROTTLING No Throttling
EXPLANATION: "ChkDsk error on the path/device specified"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-2-DISK_EJECTOR

SEVERITY : Major Alert
FORMAT : "disk ejector interrupt (pio=0x%x) -> reboot"
FLAG : Write Bram
THROTTLING : No Throttling
EXPLANATION : "Disk ejector latch caused card reboot"
RECOMMENDED ACTION: "If the disk backcard was manually removed then the event log is expected. If the event is logged and the disk was not removed then we need to investigate the root cause using logs and trace buffer dumped after reboot. One known root cause for this interrupt is a power supply glitch. This is reproducible in the lab by injecting a power supply glitch of the right interval and right voltage (voltage like 0V low gives power cycle but low voltage like 40V and the right duration gives that interrupt). So if this event is seen when disk was not removed, check that there are 2 power supplies"
REQUIRED INFO : No Required Info

SYS-4-DSKUSAGEERR

SEVERITY: Error
FORMAT: "disk usage error [%s] part=[%s] errno=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Internal error, should normally not happen"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-7-DSKUSAGEOK

SEVERITY: Information
FORMAT: "disk space OK part=[%s] freeMb=%d sizeMb=%d"
FLAG: No Flag
THROTTLING One Second
EXPLANATION: "Available disk space is back above low threshold in specified disk partition which is healthy"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SYS-3-DSKUSAGELOW

SEVERITY: Minor Alert
FORMAT: "disk space low part=[%s] freeMb=%d sizeMb=%d threshold=%d%%"
FLAG: No Flag
THROTTLING One Second
EXPLANATION: "Available disk space becomes less than a low threshold. There is still available disk. Clean the disk at least until you see the
RECOMMENDED ACTION: "remove useless files on the disk partition"
REQUIRED INFO "output of dspdisk, event logs"

SYS-2-DSKUSAGELOWSEV

SEVERITY: Major Alert
FORMAT: "disk space low part=[%s] freeMb=%d sizeMb=%d threshold=%d%%"
FLAG: No Flag
THROTTLING One Second
EXPLANATION: "Available disk space became less than severe low threshold. There is almost no disk space available. Clean the disk at least until you see the
RECOMMENDED ACTION: "remove useless files on the disk partition"
REQUIRED INFO "output of dspdisk, event logs"

DDTS "traps"

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

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

TRAP-5-INV_ADDR

SEVERITY : Warning
FORMAT : "Invalid oid_ptr:line%d:%d:%d:%d:%d:%d:0x%x:%d:%s= 0x%x:%s= 0x%x:%s= 0x%x"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "The address alignment is incorrect.The format string has the following entries:line:trapno:thisTrapSlot:thisTrapNumVars:thisTrapTyp:thisTrapSev:thisTrapOID:thisTrapSize:%s= 0x%x:%s= 0x%x:%s= 0x%x"
RECOMMENDED ACTION : No Recommended Action
REQUIRED INFO : No Required Info

TRAP-5-ERR_RETURN

SEVERITY : Warning
FORMAT : "%d:%s:%d"
FLAG : No Flag
THROTTLING : One Tick
EXPLANATION : "At line number specified, there was an error encountered as described in the format string"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO : No Required Info

TRAP-7-INVALIDINPUT

SEVERITY: Information
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

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

TRAP-7-PARMINVALID

SEVERITY: Information
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

TRAP-7-PARMINVLENGTH

SEVERITY: Information
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

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

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

TRAP-5-QUEUEFULL

SEVERITY: Warning
FORMAT: "Could not send trap %d from slotnum %d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The Trap Client Queue has reached/passed the high water mark"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

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

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

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

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

DDTS "atmsig"

NETB-5-SSIF_TIMER_INIT

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

NETB-5-SSIF_TIMER_ENAB

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

NETB-5-MAIN_EP_INIT_FA

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

NETB-5-TGM_INIT_FAILED

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

NETB-5-CLI_INIT_FAILED

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

NETB-5-EP_INIT_FAILED

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

NETB-5-UNEXPECTED_TGM_

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

NETB-5-MEMINIT_ERROR

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

NETB-5-IPC_MSG_ALLOC_F

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

NETB-5-IPC_MSG_SEND_FA

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

DDTS "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

DDTS "traps"

TRAP-4-SEM_FAILED

SEVERITY: Error
FORMAT: "Semaphore failed to give. Changing state to UNAVAIL"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to send a trap through master agent was made. The trap server application could not get a semaphore, required to make sure that the master agent is not configuring itself. The semaphore could not be taken because its creation failed. Trap server subsystem 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-4-SRV_INIT_FAILED

SEVERITY: Error
FORMAT: "Trap server initialization failed. Exiting..."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The main routine for the trap server application failed to initialize. It failed to create an EPID for receiving messages from all the AXSM cards and PXM applications. Trap server subsystem 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-5-INVOIDPTR

SEVERITY: Warning
FORMAT: "Invalid oid_ptr at line %d %s= 0x%x , %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 for the oid_ptr.If this case is hit in the trap server code, the trap will not be sent. This is done since in any case, the trap has been corrupted before getting to the server."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

TRAP-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 send the trap, trapserver found an invalid length for the OID field.Thus, this trap will be dropped by the server and not be sent."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

TRAP-5-INVPTR

SEVERITY: Warning
FORMAT: "Invalid ptr at line %d %s= 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "While attempting to send the trap, there was a NULL pointer passed. The calling application has passed invalid set of parameters to the trapserver. This corrupt/ invalid trap structure will not be sent by the server."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "ccma"

UDP-5-UDP_INIT_ERR

SEVERITY: Warning
FORMAT: "UDP Error UDP No %d function 0X%X line %d exit due to %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: " Error Caused during Initialisation of UDP"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

UDP-5-UDP_INTRPT_ERR

SEVERITY: Warning
FORMAT: "UDP Error UDP No %d function 0X%X line %d due to intrpt type %d status %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: " Specifies the Interrupts caused. The Code indicates the type of the interrupt such as the STATS_INTRPT, U3_INTRPT, U2_INTRPT and ACP interrupt. The cause indicates what interrupt occurred in each of these."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

UDP-5-UDP_GEN_ERR

SEVERITY: Warning
FORMAT: "UDP Error UDP No %d function 0X%X line %d exit due to %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: " General Error. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

UDP-5-UDP_PARAM_ERR

SEVERITY: Warning
FORMAT: "UDP Error UDP No %d function 0X%X line %d exit due to %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: " Incorrect parameter was passed to UDP driver."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "vsi"

VSI-5-VSI_MSG_LENGTH

SEVERITY: Warning
FORMAT: "VSI_MSG_LENGTH %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI msg length problem."
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

VSI-5-VSI_PG_LENGTH

SEVERITY: Warning
FORMAT: "VSI_PG_LENGTH functionCode(%4x), pgFmtId(%4x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI pg length problem."
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

VSI-5-SYNTAX_ERROR

SEVERITY: Warning
FORMAT: "VSI_SYNTAX_ERROR functionCode(%2x), msgStatus(%4x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Syntax error in parsing VSI message problem."
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

VSI-5-VSI_CONTROLLER

SEVERITY: Warning
FORMAT: "VSI_CONTROLLER %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI Controller Problem."
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

VSI-5-VSI_SAP

SEVERITY: Warning
FORMAT: "VSI_SAP %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI SAP problem."
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

VSI-5-VSI_MSGQ

SEVERITY: Warning
FORMAT: "VSI_MSGQ %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI msg queue problem."
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

VSI-5-VSI_SOCKET

SEVERITY: Warning
FORMAT: "VSI_SOCKET %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI socket problem."
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

VSI-5-VSI_UNKNOWN_CMD

SEVERITY: Warning
FORMAT: "VSI_UNKNOWN_CMD %2x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unkonown VSI command."
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

VSI-5-VSIS_TRAP

SEVERITY: Warning
FORMAT: "VSIS_TRAP %s %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI Slave trap problem."
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

VSI-7-VSIS_TX

SEVERITY: Information
FORMAT: "VSIS_TX %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI Slave transport problem."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VSI-7-NULL_PTR

SEVERITY: Information
FORMAT: "NULL_PTR at %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "NULL pointer"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VSI-5-MALLOC_FAIL

SEVERITY: Warning
FORMAT: "MALLOC_FAIL"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssiMalloc() 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

VSI-5-FREE_FAIL

SEVERITY: Warning
FORMAT: "FREE_FAIL"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssiFree() 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

VSI-5-FBALLOC_FAIL

SEVERITY: Warning
FORMAT: "MALLOC_FAIL"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssiFrameBufferAlloc() 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

VSI-5-FBFREE_FAIL

SEVERITY: Warning
FORMAT: "FREE_FAIL"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssiFrameBufferFree() 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

VSI-5-VSI_TIMER

SEVERITY: Warning
FORMAT: "VSI_TIMER %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI timer problem."
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

VSI-5-VSI_CLK

SEVERITY: Warning
FORMAT: "VSI_CLK %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "VSI clock source problem."
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

VSI-7-SSI_VSI_IF

SEVERITY: Information
FORMAT: "SSI_VSI_IF %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SSI VSI IF problem."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

DDTS "unknown"

VSI-7-E1

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

VSI-7-VSI_MSG_LENGTH

SEVERITY: Information
FORMAT: "VSI_MSG_LENGTH %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI msg length problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_PG_LENGTH

SEVERITY: Information
FORMAT: "VSI_PG_LENGTH functionCode(%4x), pgFmtId(%4x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI pg length problem"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_SYNTAX_ERRO

SEVERITY: Information
FORMAT: "VSI_SYNTAX_ERROR functionCode(%2x), msgStatus(%4x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI syntax problem"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_CONTROLLER

SEVERITY: Information
FORMAT: "VSI_CONTROLLER %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI Controller Problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_SAP

SEVERITY: Information
FORMAT: "VSI_SAP %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI SAP problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_MSGQ

SEVERITY: Information
FORMAT: "VSI_MSGQ %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI msg queue problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_SOCKET

SEVERITY: Information
FORMAT: "VSI_SOCKET %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI socket problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_UNKNOWN_CMD

SEVERITY: Information
FORMAT: "VSI_UNKNOWN_CMD %2x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unkonown VSI command."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSIS_TRAP

SEVERITY: Information
FORMAT: "VSIS_TRAP %s %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI Slave trap problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSIS_TX

SEVERITY: Information
FORMAT: "VSIS_TX %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI Slave transport problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-NULL_PTR

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

VSI-7-MALLOC_FAIL

SEVERITY: Information
FORMAT: "MALLOC_FAIL"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiMalloc() failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-FREE_FAIL

SEVERITY: Information
FORMAT: "FREE_FAIL"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiFree() failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-FBALLOC_FAIL

SEVERITY: Information
FORMAT: "MALLOC_FAIL"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiFrameBufferAlloc() failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-FBFREE_FAIL

SEVERITY: Information
FORMAT: "FREE_FAIL"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiFrameBufferFree() failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_TIMER

SEVERITY: Information
FORMAT: "VSI_TIMER %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI timer problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_CLK

SEVERITY: Information
FORMAT: "VSI_CLK %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI clock source problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSI-7-VSI_ROOT

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

VSI-7-VSI_PROXY

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

VSI-7-VSIM_PROXY

SEVERITY: Information
FORMAT: " %s %d VSIM PROXY %d %p %s "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VSI master proxy event"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "vsim"

VSIM-5-VSIM_DEBUG

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

VSIM-7-VSIM_INFO

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

VSIM-7-VSIM_STATS

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

VSIM-6-VSIM_NOTICE

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

DDTS "vsim"

VSIM-5-VSIM_DEBUG

SEVERITY: Warning
FORMAT: "VSIM DEBUG %s"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSIM-7-VSIM_INFO

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

VSIM-7-VSIM_STATS

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

VSIM-6-VSIM_NOTICE

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

DDTS "pxm-connmgm"

VSIS-7-VSIS_MSGQ

SEVERITY: Information
FORMAT: "VSI_MSGQ%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This event is currently not being used in the baseline. However, any engineer who uses this event should modify this explanation and describe the context of the event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSIS-7-VSIS_PXMCM_MSGP

SEVERITY: Information
FORMAT: "%s Line %d A null msg pointer detected "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This event occured due to a null msg pointer recevied during a pass up/down response "
RECOMMENDED ACTION: "This is just an informational event "
REQUIRED INFO No Required Info

DDTS "vsi"

VSIS-7-VSIS_MSGQ

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

DDTS "vsi"

VSIS-7-VSIS_MSGQ

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

DDTS "vsi"

VSIS-7-VSIS_MSGQ

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

VSIS-7-INFO_STR

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

DDTS "pxm-connmgm"

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-5-VSIERRCODE

SEVERITY: Warning
FORMAT: "VSI Error Module %s Function %d Code %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This event is not use at the moment. Please modify this explanation once you use this event"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSIC-2-VSIMAJORERR

SEVERITY: Major Alert
FORMAT: "%s, Vsi PXM Major Alert %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This error gets logged to indicate TCB error or error upda- ting connections on the standby PXM. It may indicate that some connections are not programmed correctly on active or standby PXM"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/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

PXMC-4-RAMSYNC

SEVERITY: Error
FORMAT: "%s, line %d PXMCM Ram Sync %s error - errno = 0x%x, resetCause = %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This error is logged while updating the standby PXM. If errno = 0x20903, it indicates that standby was reset while bulk sync was in progress & no action needs to be taken. Any other errno needs to be analyzed by TAC and possibly by the development team. This error usually indicates an error while updating the standby PXM "
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/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

PXMC-4-GENERR

SEVERITY: Error
FORMAT: "%s, line %d PXMCM %s "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This is an internal error reported by the PXMCM module. This is a general error , the error log itself will indicate the nature of the problem"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/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 Tick
EXPLANATION: "VSIS General errors"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Flag

VSIS-4-NFMAJERR

SEVERITY: Error
FORMAT: "%s, line %d Putting card in slot %d in Non Fatal Major Err\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This event indicates an error while updating connections or inteface policy to the standby PXM card. The Standby PXM card will be reset or put in the failed state. "
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/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-4-GENERR

SEVERITY: Error
FORMAT: "%s, line %d Vsi Slave %s error"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This is an internal error reported by the VSIS module. It indcates an error associated with adding or deleting a TAG cont- roller."
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

DDTS "atmsig"

VSM-4-SIGAPIINITERR

SEVERITY: Error
FORMAT: "%s Could not resolve SigAPI Queue!\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to initilize sigapi end point. VSM can't 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 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.

VSM-6-SAPIMSGARR

SEVERITY: Notice
FORMAT: "SAPI %s message received from Client ID %d Call Ref %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-6-SIGAPIMSGARR

SEVERITY: Notice
FORMAT: "SigApi %s message received for Client ID %d Call Ref %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-6-NEWCLIENT

SEVERITY: Notice
FORMAT: "A new client has sent a RESTART request to VSM. Client Id %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-6-SAPIRESTART

SEVERITY: Notice
FORMAT: "Client %d has sent a RESTART request with reason %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-6-CLIENTSTATECHAN

SEVERITY: Notice
FORMAT: "%s Client %d changed from state %d to state %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-6-BULKRESYNC

SEVERITY: Notice
FORMAT: "%s Received Bulk Resynch Record from Client Id %d of size %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-6-STATECHANGE

SEVERITY: Notice
FORMAT: "%s Call %d changed from state %d to state %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-4-INVCALLREF

SEVERITY: Error
FORMAT: "%s Invalid Call Reference Value passed in SAPI Header"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Call Reference Value set in signalling 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
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.

VSM-4-SIGAPIERROR

SEVERITY: Error
FORMAT: "%s Could not send SigApi message"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Due to IPC problem, Could not send message to signalling call control. VSM couldn't 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 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.

VSM-4-SAPIERROR

SEVERITY: Error
FORMAT: "%s Could not send SAPI message"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Due to IPC problem, Could not send message to SAPI layer. VSM counld't 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 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.

VSM-4-WRONGEVENTFORST

SEVERITY: Error
FORMAT: "%s Wrong event received for state %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Software error -- Unexpected event received in current state"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO 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.

VSM-4-DUPRECORDERR

SEVERITY: Error
FORMAT: "%s Duplicate record found in tree. Call Ref %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Duplicate record found. Failed to Insert new call record. Previous record delete msg may not reached to standby"
RECOMMENDED ACTION: Copy the error message 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.

VSM-4-MISSINGRECORD

SEVERITY: Error
FORMAT: "%s Record missing from tree. Call Ref %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The Call Record is some how missing due to software error or corruption"
RECOMMENDED ACTION: Copy the error message 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.

VSM-4-RECINSERR

SEVERITY: Error
FORMAT: "%s Error inserting Record into tree %s. Call Ref %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to insert new call record into progress list."
RECOMMENDED ACTION: Copy the error message 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.

VSM-4-RECALLOCERR

SEVERITY: Error
FORMAT: "%s Error allocating memory for call record"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Could not allocate memory for call record"
RECOMMENDED ACTION: Copy the error message 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.

VSM-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.

VSM-7-ADDRSUCC

SEVERITY: Information
FORMAT: "Address Regsistration successful %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Informative Event Log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-4-ADDRERR

SEVERITY: Error
FORMAT: "Address Regsistration ERROR %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Address Registration Error. May not be able to process calls regarding it"
RECOMMENDED ACTION: Copy the error message 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.

VSM-4-UNSUPMSGTYPE

SEVERITY: Error
FORMAT: "%s SigApi sent us a message that VSM does not support %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Software Error -- Unexpected message get passed from Signalling. "
RECOMMENDED ACTION: Copy the error message 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.

VSM-4-RESOLVERR

SEVERITY: Error
FORMAT: "%s Could not resolve IPC Queue Name %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Could not resolve IPC Endpoint for signalling messages"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO 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.

VSM-4-IPCMSGERR

SEVERITY: Error
FORMAT: "%s Could not %s IPC message"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "IPC errors. VSM can not be function with signalling"
RECOMMENDED ACTION: Copy the error message 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.

VSM-4-INACTIVECLIENT

SEVERITY: Error
FORMAT: "%s Accessed a client record of an inactive client %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The client is not activated, calls of this client can not be processed."
RECOMMENDED ACTION: Copy the error message 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.

VSM-4-INVCLIENTID

SEVERITY: Error
FORMAT: "%s Client Id Out of Range %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Software Error -- Trying to get a client record with out of range client 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
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.

VSM-4-INVSC

SEVERITY: Error
FORMAT: "%s Invalid Service Category %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Service Category get passed from signalling 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.

VSM-4-TIMERERROR

SEVERITY: Error
FORMAT: "%s Could not %s timer\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Could not create or start 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
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.

VSM-6-CHECKSUM

SEVERITY: Notice
FORMAT: "Checksum %d received from Client is %s to %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-6-BULK_RESYNC

SEVERITY: Notice
FORMAT: "%s Bulk resync record received for call ref %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

VSM-6-SIGAPIMSGSENT

SEVERITY: Notice
FORMAT: "%s SIG Api message sent. Opcode %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Informative event log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "pxm-connmgm"

VCNM-4-INIT_FAIL

SEVERITY: Error
FORMAT: "VCNM pipc port create failed err %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Initialization failure."
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

VCNM-7-UNKNOWN_MSG

SEVERITY: Information
FORMAT: "VCNM Unknown pipc message received, msgType = %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown message received."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VCNM-7-UNKNOWN_TASK

SEVERITY: Information
FORMAT: "VCNM Message received with Invalid Task Id = %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Event received from unknown task."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

CMM-4-INIT_ERROR_CMM

SEVERITY: Error
FORMAT: "Init Error %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "CMM/VSM initialization 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 No Required Info

CMM-5-GET_MSG_ERROR

SEVERITY: Warning
FORMAT: "Get Message %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in receiving 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 No Required Info

CMM-4-GET_EVENT_ERROR

SEVERITY: Error
FORMAT: "Get Event %s, %d "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in receiving event."
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

CMM-5-UNKNOWN_MSG

SEVERITY: Warning
FORMAT: "UNknown message %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown message received."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

CMM-5-RCV_MSG_FAILED

SEVERITY: Warning
FORMAT: "Init Error %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in receiving messages."
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

CMM-5-INVALID_SLOT_NO

SEVERITY: Warning
FORMAT: "Invalid Slot Number, %s, %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The input parameter to this function was invalid."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

CMM-7-SLOT_NO_SET

SEVERITY: Information
FORMAT: "updateSlotNum Old S.N.= %d New S.N.=%d "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Slot number is successfully set."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VSM-4-DISK_UPD_FAIL

SEVERITY: Error
FORMAT: "VSM %s PXM Disk Update Failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Disk update 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

VSM-4-VSM_UNDO_DEL_BB

SEVERITY: Error
FORMAT: "VSM %s Undo Port delete Failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Undo Port Delete 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

VSM-4-VSM_UNDO_MOD_BB

SEVERITY: Error
FORMAT: "VSM %s Undo Port modify Failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Undo Port Modify 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

VSM-4-VSM_UNDO_BBIF_F

SEVERITY: Error
FORMAT: "VSM %s Undo Port Failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Undo Port 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

VSM-7-VSM_BBIF_ADDED

SEVERITY: Information
FORMAT: "VSM Broadband Interface %d Added"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "BBIF successfully added."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VSM-7-VSM_BBIF_DEL

SEVERITY: Information
FORMAT: "VSM Broadband Interface %d Deleted"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Deleted BBIF successfully."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VSM-7-VSM_BBIF_MOD

SEVERITY: Information
FORMAT: "VSM Broadband Interface %d Modified"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Modified BBIF successfully."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VSM-7-VSM_RSC_CNF_CHG

SEVERITY: Information
FORMAT: "VSM Conf Chg in Rsc Partition ifNum %d, ctrlr %d, rowStat %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Configuration change occurred."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VSM-7-BBCHAN_ADDED

SEVERITY: Information
FORMAT: "VSM Broadband Channel %d Added"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "BB channel has been successfully added."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VSM-7-BBCHAN_DELETED

SEVERITY: Information
FORMAT: "VSM Broadband Channel %d Deleted"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "BB channel has been successfully deleted."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

DDTS "unknown"

VCNM-4-INIT_FAIL

SEVERITY: Error
FORMAT: "VCNM pipc port create failed err %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Initialization failure."
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

VCNM-7-UNKNOWN_MSG

SEVERITY: Information
FORMAT: "VCNM Unknown pipc message received, msgType = %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown message received."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

VCNM-7-UNKNOWN_TASK

SEVERITY: Information
FORMAT: "VCNM Message received with Invalid Task Id = %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Event received from unknown task."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

CMM-4-INIT_ERROR_CMM

SEVERITY: Error
FORMAT: "Init Error %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "CMM/VSM initialization 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 No Required Info

CMM-4-GET_MSG_ERROR

SEVERITY: Error
FORMAT: "Get Message %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in receiving 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 No Required Info

CMM-4-GET_EVENT_ERROR

SEVERITY: Error
FORMAT: "Get Event %s, %d "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in receiving event."
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 informati