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

FIPC-4-MBLKBUFDESCERR

Table Of Contents

FIPC-4-MBLKBUFDESCERR

FIPC-5-DBUFSIZEINVALID

FIPC-4-MBLKALLOCFTLERR

FIPC-4-MBLKINVALID

FIPC-4-MBLKASSIGNFAIL

FIPC-5-MBLKUNAVAILABLE

FIPC-5-MBLKENQUEUED

FIPC-4-MBLKNOHDRSPACE

FIPC-4-MBLKBUFFREEFAIL

FIPC-4-MBLKFREEFAIL

FIPC-4-BUFSZERR

FIPC-5-LINKINERROR

FIPC-5-LINKOUTERROR

FIPC-4-LINKMEMALLOCERR

FIPC-5-LINKSARREGERROR

FIPC-5-LINKPLFMSLOT2RX

FIPC-5-SMSLOTERROR

FIPC-5-CTLDUPMSGFAIL

FIPC-5-CTLALLOCMSGFAIL

FIPC-4-CTLRCVEPIDERR

FIPC-4-CTLCOMEPERR

FIPC-4-CTLSYNCTMRERR

FIPC-4-CTLRETXQERR

FIPC-4-CTLHDLRATTCHERR

FIPC-4-CTLEPWAITERR

FIPC-5-CTLINVMSGTYPE

FIPC-5-CTLINVMSGVER

FIPC-5-CTLRCVMSGERR

FIPC-5-CTLTSKCREATEERR

FIPC-5-RSLVACKERR

FIPC-5-RSLVNAMELENERR

FIPC-5-CTLOUTOFMBLKS

FIPC-5-CTLBINDSTUNKN1

FIPC-5-CTLBINDSTUNKN2

FIPC-5-CTLBINDSTUNKN3

FIPC-5-CTLBINDSTUNKN4

FIPC-5-CTLBINDSTUNKN5

FIPC-4-CTLBINDSTFAIL1

FIPC-4-CTLBINDSTFAIL2

FIPC-4-CTLBINDSTFAIL3

FIPC-4-CTLUNBINDSTFAIL

FIPC-5-CTLUNBINDSTUNKN

FIPC-4-CTLMAXBUFRPLYER

FIPC-4-CTLINVIPCVER

FIPC-4-CTLINVRMTCTLMSG

FIPC-4-NAMEMEMALLOC

FIPC-4-NAMESRCSLOTINV

FIPC-4-NAMETASKCREATE

FIPC-4-NAMECOMEPCREATE

FIPC-5-NAMEINVMSGTYPE

FIPC-4-NAMEINVMSGVER

FIPC-5-NAMEENTRYOVRRID

FIPC-4-NAMEENTRYINIT

FIPC-4-NAMEARRAYFULL

FIPC-4-NAMEMSGALLCFAIL

FIPC-5-NAMEENTRYBNDINV

FIPC-5-NAMENOENTRYOUT

FIPC-5-LCNOUTOFRANGE

FIPC-4-LCNALREADYBOUND

FIPC-5-LCNSARREGFAILED

FIPC-5-LCNSARUNREGFAIL

FIPC-5-LCNEPIDINVALID

FIPC-5-LCNOWNERINVALID

FIPC-5-LCNNOTBOUND

FIPC-5-LCNMSGSENDERROR

FIPC-5-CONNREF_INVALID

FIPC-4-CONNADD_FAIL

FIPC-4-CONNDEL_FAIL

FIPC-4-LCNBIND_FAIL

FIPC-4-LCNUNBIND_FAIL

FIPC-4-CTCSTATETRAFAIL

FIPC-4-CTCEVTREGFAIL

DDTS "stats-upload"

STAT-1-FATAL_ERROR

STAT-4-MAJOR_ERROR

STAT-4-ERROR

STAT-5-WARNING

DDTS "ssi"

SRAP-4-IOV_NOTFREED

SRPR-4-INVALID_PDU

SRPR-4-INVALID_PDUVER

SRPR-4-INVALID_UNBLOCK

SRPR-5-INVALID_INIT

SRPR-4-FAILED_CTCCALL

SRPR-4-INVALID_CTCEVT

SRPR-4-INV_CTC_RETVAL

SRPR-4-INVALID_SM_LOCK

SRPR-4-SM_LOCK_TIMEOUT

SRPR-4-INVALID_SMUNLCK

SRPR-4-INVALID_BLOCK

SRPR-4-INVALID_DBID

SRPR-5-SR_DBIDWARN

SRPR-5-INVALID_EVENT

SRPR-4-SR_IPCERR

SRPR-4-INVALID_EVTFUNC

SRPR-4-SR_NO_RSRC

SRPR-5-SR_IPCWARNING

SRPR-7-SR_SYNCDONE

SRPR-7-ACK_TIMEOUT

SRPR-5-SR_BADREG

DDTS "ssi"

SRAP-7-NO_EVENT

SRAP-4-API_INVALIDPARM

SRAP-5-API_INVALIDPARM

SRAP-5-INVALID_DBNAME

SRAP-5-INVALID_DBID

SRAP-5-INVALID_WINSIZE

SRAP-5-INVALID_RECSIZE

SRAP-5-INVALID_REREG

SRAP-5-TOOMANYCONS

SRAP-5-INV_IOVMAXELEMS

SRAP-5-FAILED_BUFALLOC

SRAP-5-INVALID_IOVSIZE

SRAP-5-INVALID_TID

SRAP-5-INV_APPSTATE

SRAP-5-INVALID_APICALL

SRAP-5-BAD_RESETACK

SRAP-5-INVALID_EPID

SRAP-4-FAILED_PROTOEVT

SRAP-5-INVALID_FUNC

SRAP-5-INVALID_EVTREG

SRAP-5-IOV_INVLDIOVHDR

SRAP-5-IOV_NUMELEMINV

SRAP-4-IOV_BUFHDRINVLD

SRAP-5-IOV_BUFVERINVLD

SRAP-5-IOV_BUFSIZEINV

SRAP-5-IOV_BUFLIMITINV

SRAP-4-IOV_BUFFERFREE

SRAP-4-IOV_ELEMDATALEN

SRAP-5-IOV_ACCFUNCERR

SRAP-4-IOV_NOACCFUNC

SRAP-4-IOV_ELEMTYPEINV

SRAP-4-IOV_ELEMBUFFER

SRAP-4-IOV_ELEMOFFSET

SRAP-4-IOV_DUPFAILED

SRAP-5-IOV_HDRDUPFAIL

SRAP-7-IOV_STBY_SEND

SRAP-5-IOV_STBY_SEND_F

SRAP-5-INVALID_EVTFUNC

SRAP-2-API_CONV_FUNC_F

SRAP-5-API_CONV_MAJ_FA

SRAP-5-API_CONV_MAJ_FA

SRAP-5-API_CONV_MAJ_FA

SRAP-3-API_CONV_MAJ_FA

SRAP-5-API_CONV_MAJ_FA

SRAP-2-API_CONV_FATAL_

SRAP-2-API_CONV_FATAL_

SRAP-5-API_CONV_FATAL_

SRAP-5-API_CONV_FATAL_

SRAP-5-API_CONV_FATAL_

SRAP-5-API_CONV_FAIL

SRAP-5-API_CONV_FAIL2

SRAP-2-API_CONV_FAIL3

SRAP-4-API_CONV_FAIL4

SRAP-4-API_CONV_FAIL5

SRAP-5-API_CONV_WARNIN

SRAP-5-API_CONV_WARNIN

SRAP-4-IOV_INVLDPTR

DDTS "diskdb"

DB2A-5-DB2API_APPL_ID

DB2A-5-DB2API_MSG_BUF_

DB2A-5-DB2API_MSG_BUF_

DB2A-5-DB2API_SYN_MSG_

DB2A-5-DB2API_MSG_SEND

DB2A-5-DB2API_WRONG_RE

DB2A-5-DB2API_REPLY

DB2A-5-DB2API_INVNAME

DB2A-5-DB2API_INVPARAM

DB2A-5-DB2API_INVPTR

DB2A-5-DB2API_INV_LSLO

DB2A-5-DB2API_INV_SVR_

DB2A-5-DB2API_INV_SVR_

DB2A-7-STBYRDENABLE

DB2A-7-STBYRDDISABLE

DB2A-7-REG

DDTS "ssi"

SSI-2-MAJOR_ERROR

SSI-5-ERROR_STKYES

SSI-5-ERROR_STKNO

SSI-4-PARMINVALID

SSI-4-PARMMAXEXCEEDED

SSI-4-PARMOUTOFRANGE

SSI-4-TASKENTRYGETFAI

SSI-4-TASKIDINVALID

SSI-4-TASKSEMINVL

SSI-4-TASKSEMTAKE

SSI-4-TASKSEMGIVE

SSI-4-TASKSEMCREATE

SSI-4-TASKSEMDEL

SSI-4-TIMERERROR

SSI-4-TIMEREVENT

SSI-4-CHUNKINVPTR

SSI-6-RESETDUMPTRACE

SSI-3-EXCEPTION

SSI-4-ISRNOTCALLABLE

SSI-4-ISRNOTCLBLEPC

SSI-4-TBLSEMTAKEFAIL

SSI-5-OBJCREATENOMEM

SSI-5-SEMTBLFULL

SSI-4-SEMDAINVALID

SSI-4-SEMTYPEINVALID

SSI-4-SEMOPTINVALID

SSI-4-SEMSTATEINVALID

SSI-5-SEMCREATEFAIL

SSI-4-SEMIDINVALID

SSI-5-SEMIDDELETED

SSI-5-SEMDELUNOWN

SSI-4-SEMDELFAIL

SSI-4-SEMTAKEFAIL

SSI-4-SEMGIVEUNOWN

SSI-4-SEMGIVEFAIL

SSI-4-SEMFLUSHINV

SSI-4-SEMFLUSHFAIL

SSI-5-MQTBLFULL

SSI-4-MQMAXINVALID

SSI-4-MQMLENINVALID

SSI-4-MQOWNERINVALID

SSI-4-MQOWNERNOTEXIST

SSI-5-MQCREATEFAIL

SSI-5-MQSEMCRTFAIL

SSI-5-MQIDINVALID

SSI-5-MQIDDELETED

SSI-4-MQQUOTAINVALID

SSI-4-MQSEMDELFAIL

SSI-4-MQDELFAIL

SSI-4-MQFLSHRECVFAIL

SSI-4-MQSENDLENINV

SSI-4-MQSENDFAIL

SSI-4-MQSEMGIVEFAIL

SSI-4-MQISRSENDNZTO

SSI-4-MQRECVLENINV

SSI-4-MQRECVFAIL

SSI-4-MQSEMTAKEFAIL

SSI-4-MQHNDLRINVALID

SSI-5-MQHNDLRFAIL

SSI-4-MQNUMMSGFAIL

SSI-4-MQINFOPTRINV

SSI-4-MQINFOFAIL

SSI-5-TASKTBLFULL

SSI-4-TASKSEMGIVEFAIL

SSI-5-TASKINITPTO

SSI-5-TASKINITFAIL

SSI-4-TASKIDINVALID

SSI-5-TASKIDDELETED

SSI-4-TASKDELFAIL

SSI-5-TASKDELSAFE

SSI-5-TASKFORCEDESTRO

SSI-4-TASKRESUMEFAIL

SSI-4-TASKSUSPENDFAIL

SSI-5-TASKSUSPENDSAFE

SSI-4-TASKRESTARTFAIL

SSI-4-TASKPRIOINVALID

SSI-4-TASKPGRPINVALID

SSI-4-TASKAPPLINVALID

SSI-4-TASKSTKSIZEINV

SSI-4-TASKSUSPACTINV

SSI-4-TASKFAILACTINV

SSI-5-TASKSEMCRTFAIL

SSI-5-TASKSPAWNFAIL

SSI-5-TASKINITACKTO

SSI-4-TASKWACKFAIL

SSI-5-TASKDELMQOWN

SSI-4-INVPPARTPTR

SSI-4-THREEPART

SSI-5-MALLOC

SSI-5-NOSEMAPHORE

SSI-4-INVTYPE

SSI-4-INVOPTION

SSI-4-ZEROSIZE

SSI-4-INVLENGTH

SSI-5-BELOWTHRES

SSI-6-CROSSTHRES

SSI-5-NOPARTITION

SSI-5-NOTOWNER

SSI-5-FREESTATICWARN

SSI-5-MEMPARTCREATE

SSI-5-MEMPARTFREE

SSI-4-MEMBLKERROR

SSI-4-STRANGEADDR

SSI-4-CKINVWRDADD2

SSI-4-INVMEMTYPE

SSI-4-INVLENGTH1

SSI-4-INVMAGICCOOKIE

SSI-4-INVREFCOUNT

SSI-4-INVVXWORKPART

SSI-4-INVPARTINDEX

SSI-5-DOWNSTATIC

SSI-5-DOWNVXWORKS

SSI-4-INVPARTADDR

SSI-5-CHECKFREEBLOCK

SSI-5-FILLCHECKSEMFAI

SSI-5-TIMERTBLFULL

SSI-4-TIMERHANDLER

SSI-4-TIMERNOCREATE

SSI-4-TIMERNOCONNECT

SSI-4-TIMERNOCANCEL

SSI-4-TIMERNODELETE

SSI-4-TIMERINVALIDID

SSI-4-TIMERINVALIDENT

SSI-4-TIMERINVALIDTSK

SSI-4-TIMERINVALIDVAL

SSI-4-TIMERNOSETGET

SSI-4-TIMERSIGERROR

SSI-4-TIMERINVTOD

SSI-4-MKTIMEFAIL

SSI-4-PUTENVFAIL

SSI-4-WDALRCRT

SSI-4-WDCREATEFAIL

SSI-4-WDSTARTFAIL

SSI-5-TMRCANCELINV

SSI-4-TMRNOTINIT

SSI-5-TMRHNDLRFAIL

SSI-5-TMRKEYNOTUNIQ

SSI-5-POP1HDRERROR

SSI-5-IPCMSGERROR

SSI-5-POP1TRLERROR

SSI-5-SSISARTXERROR

SSI-5-CTCSENDMSGERROR

SSI-5-EVENTGENERROR

SSI-5-THRESHSETERROR

SSI-4-INVALIDTHRESHID

SSI-4-STRTOOLONG

SSI-4-APIERROR

SSI-5-DOSFAIL

SSI-5-DOSWRITEFAIL

SSI-5-DOSFAIL1

SSI-4-INTERNALFAIL

SSI-4-SEMFAIL

SSI-4-FILENOTOPEN

SSI-4-FDCORRUPT

SSI-4-APPNOTOWNER

SSI-5-DIO_GEN_ERROR

SSI-5-DIO_DIRCPY_ERRO

SSI-4-STKCHK

SSI-5-SSITRACEDROP

SSI-1-TEXTCORR

SSI-4-ME_SEMCREATEFAI

SSI-7-ME_SEMTAKEFAIL

SSI-5-ME_SEMGIVEFAIL

REQUIRED INFO "Take core dump. Collect event and eSSI-5-ME_OPTBLFULL

SSI-4-ME_DUPLENTRY

SSI-4-ME_INVALIDOPKEY

SSI-4-ME_TASKNOTOWNER

SSI-5-ME_LOCKFAIL

SSI-4-ME_UNLOCKFAIL

SSI-4-ME_INDEXFAIL

SSI-5-ME_INTPARMINVAL

SSI-5-ME_TASKSAFEFAIL

SSI-4-ME_TASKUNSAFEFA

SSI-7-CHNK_UNIT_TEST

SSI-7-CHNK_GROW_SHRIN

SSI-7-CHNK_FREE_LEAK

SSI-5-CHNK_LOW_PRIO

SSI-5-CHNK_STATE_LOW

SSI-7-CHNK_STATE_OK

SSI-4-CHNK_UNIQ_NAME

SSI-4-CHNK_ALRDY_GROW

SSI-4-CHNK_POOL_INV

SSI-4-CHNK_SUBPOOL_IN

SSI-4-CHNK_INV

SSI-4-CHNK_TOO_MNY_PO

SSI-4-CHNK_XNOT_USED

SSI-4-CHNK_NOT_USED

SSI-4-CHNK_POOL_NOT_F

SSI-4-CHNK_INV_PARAM

SSI-4-CHNK_INT_ERROR1

SSI-4-CHNK_INT_ERROR2

SSI-4-CHNK_INT_ERROR3

SSI-4-CHNK_INT_ERROR4

SSI-4-CHNK_REF_COUNT

SSI-4-CHNK_INV_DATA_P

SSI-4-CHNK_WRONG_TID

SSI-4-CHNK_PERM_TID

SSI-4-CHNK_PERM_CTC

SSI-4-CHNK_XCORR

SSI-4-CHNK_CORR

SSI-4-CHNK_XCTOR

SSI-4-CHNK_CTOR

SSI-4-CHNK_ISR_POOL

SSI-4-CHNK_SHARED_POO

SSI-4-CHNK_EXT_HDR

SSI-4-CHNK_UNUSED_POO

SSI-5-CHNK_FULL_POOL

SSI-5-CHNK_GROW_ATTEM

SSI-4-CHNK_GROW_FAIL

SSI-4-CHNK_INT_CNTXT

SSI-4-CHNK_INV_FREE_P

SSI-5-POP1NOROOM

SSI-5-INVMAGIC

SSI-4-SYSMEMLOW

SSI-7-SYSMEMOK

SSI-7-ISR_XBAR_ERR_RE

SSI-5-CHNK_HI_PRIO

SSI-5-SEMGIVEFORCE

DDTS "ssi"

EVEN-5-EVTLOGTST001

DDTS "ssi"

SSI_-4-INVALIDPARAM

SSI_-4-DEVSIZE

SSI_-4-DEVOPEN

SSI_-4-DEVIOCTL

SSI_-3-SSIMALLOC


FIPC-4-MBLKBUFDESCERR

SEVERITY: Error
FORMAT: "Failed to alloc FIPC buffer descriptor memory (num buf desc %d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to allocate FIPC buffer"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-DBUFSIZEINVALID

SEVERITY: Warning
FORMAT: "Requested data buffer size %d exceeds system max buffer size"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Requested data buffer size exceeds the system max buf size"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-4-MBLKALLOCFTLERR

SEVERITY: Error
FORMAT: "Fatal error %x allocating floating mblk, mblk control corrupted "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Fatal error while allocating floating mblk, mblk, control corrupted"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-MBLKINVALID

SEVERITY: Error
FORMAT: "Invalid message descriptor"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Invalid message descriptor"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-MBLKASSIGNFAIL

SEVERITY: Error
FORMAT: "Message assignment failed %s %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Message assignment failed"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-MBLKUNAVAILABLE

SEVERITY: Warning
FORMAT: "No mblk available for a buffer - mblk pool corrupted"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "No mblk available for a buffer - mblk pool corrupted"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-MBLKENQUEUED

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

FIPC-4-MBLKNOHDRSPACE

SEVERITY: Error
FORMAT: "No space for header, errno %x, Wanted %d, Got %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "No space for header"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-MBLKBUFFREEFAIL

SEVERITY: Error
FORMAT: "Failed to free data buffer %x, errno %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to free data buffer"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-MBLKFREEFAIL

SEVERITY: Error
FORMAT: "Failed to free mblk %x, errno %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to free mblk"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-BUFSZERR

SEVERITY: Error
FORMAT: "%s Failed to get padding size for chunk data size %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The padding size could not be determined for the given chunk data size. This is an internal error."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-LINKINERROR

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

FIPC-5-LINKOUTERROR

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

FIPC-4-LINKMEMALLOCERR

SEVERITY: Error
FORMAT: "Failed to allocate memory for link cfg table (num links %d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to allocate memory for link config table"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-LINKSARREGERROR

SEVERITY: Warning
FORMAT: "%d Error %x registering link %d (slot %d) lcn=0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error encountered in registering link"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-LINKPLFMSLOT2RX

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

FIPC-5-SMSLOTERROR

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

FIPC-5-CTLDUPMSGFAIL

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

FIPC-5-CTLALLOCMSGFAIL

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

FIPC-4-CTLRCVEPIDERR

SEVERITY: Error
FORMAT: "Error getting caller task's Receive Sync Epid"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error encountered in getting the caller task's receive Sync Endpoint Id"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLCOMEPERR

SEVERITY: Error
FORMAT: "Error %x instantiating FIPC Control Port"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error instantiating FIPC control port"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLSYNCTMRERR

SEVERITY: Error
FORMAT: "%s Error %x initializing FIPC Sync Timer"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error initializing FIPC sync timer"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLRETXQERR

SEVERITY: Error
FORMAT: "Error %x initializing FIPC Retransmission Queue"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error Initializing FIPC retransmission queue"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLHDLRATTCHERR

SEVERITY: Error
FORMAT: "Error %x attaching EP Wait handler to IPC Ctl queue"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error attaching EP wait handler to IPC ctl queue"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLEPWAITERR

SEVERITY: Error
FORMAT: "Error %x exiting from EP Wait handler"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error exiting from EP wait handler"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-CTLINVMSGTYPE

SEVERITY: Warning
FORMAT: "Invalid FIPC Ctl msg type %x, arg %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid FIPC control message type"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLINVMSGVER

SEVERITY: Warning
FORMAT: "Invalid FIPC Control msg version %x, arg %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid FIPC control message version"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLRCVMSGERR

SEVERITY: Warning
FORMAT: "Error %x receiving FIPC Ctl message"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error encountered in receiving FIPC control message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLTSKCREATEERR

SEVERITY: Warning
FORMAT: "Error %x creating FIPC Control Task"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error encountered in creating FIPC control task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-RSLVACKERR

SEVERITY: Warning
FORMAT: "Received msg %x instead of RESOLVE ACK, arg %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Received message instead of Resolve Ack"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-RSLVNAMELENERR

SEVERITY: Warning
FORMAT: "Requested FIPC Global Name \"%s\" too long (max name len %d )"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Name to be resolved too long"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLOUTOFMBLKS

SEVERITY: Warning
FORMAT: "FIPC Control could not allocate mblk"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "FIPC control could not allocate memory block"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLBINDSTUNKN1

SEVERITY: Warning
FORMAT: "Epid %x Bind st. unknown, error %x sending duped BIND Rqst"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown error encountered while sending duped BIND request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLBINDSTUNKN2

SEVERITY: Warning
FORMAT: "Epid %x Bind state unknown, error %x receiving BIND Ack"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown Bind state while receiving BIND Ack"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLBINDSTUNKN3

SEVERITY: Warning
FORMAT: "Epid %x Bind state unknown, error %x putting BIND Rqst on RetxQ"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown Bind state while putting BIND request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLBINDSTUNKN4

SEVERITY: Warning
FORMAT: "Epid %x Bind st unknown, unknown sts %x in BIND Ack, errno %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown Bind state in BIND Ack"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CTLBINDSTUNKN5

SEVERITY: Warning
FORMAT: "Epid %x Bind state unknown, error %x retransmitting BIND Rqst"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown Bind state while retransmitting BIND request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-4-CTLBINDSTFAIL1

SEVERITY: Error
FORMAT: "Epid %x Bind state failed, error %x sending to Name Svr"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Bind request failed because of error while sending to Name server"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLBINDSTFAIL2

SEVERITY: Error
FORMAT: "Epid %x Bind state failed, error %x - out of mblks"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Bind state failed due to an outage of memory blocks"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLBINDSTFAIL3

SEVERITY: Error
FORMAT: "Epid %x error %x binding global name"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Bind request failed because it was invalid"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLUNBINDSTFAIL

SEVERITY: Error
FORMAT: "Epid %x UnBind state failed, error %x sending to Name Svr"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in unbind because of send request failed to Name server"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-CTLUNBINDSTUNKN

SEVERITY: Warning
FORMAT: "Epid %x UnBind st. unknown, error %x sending duped UNBIND Rqst"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown Unbind state while sending duped UNBIND request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-4-CTLMAXBUFRPLYER

SEVERITY: Error
FORMAT: "Error in Replying to Query for MaxBufSize, error %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Reply to Remote Card Query for Buffer Size Failed"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLINVIPCVER

SEVERITY: Error
FORMAT: "Ipc Version of Remote Card %d is different"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Message to Remote Card failed, different IPC version"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTLINVRMTCTLMSG

SEVERITY: Error
FORMAT: "Remote Card IPC CtlMsg Version Invalid"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Message to Remote Card failed, diff IPC Ctl version"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-NAMEMEMALLOC

SEVERITY: Error
FORMAT: "Failed allocate memory for %s, maxNumNames %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to allocate memory for global name array"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-NAMESRCSLOTINV

SEVERITY: Error
FORMAT: "Name Server BIND Rqst from slot %d Epid's srcPhySlotId %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Bind request invalid because of slot mismatch"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-NAMETASKCREATE

SEVERITY: Error
FORMAT: "Failed to create Name Server task, errno %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to create Name Server task"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-NAMECOMEPCREATE

SEVERITY: Error
FORMAT: "Failed to instantiate name Server Comm endpoint, errno %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to instantiate name server comm endpoint"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-NAMEINVMSGTYPE

SEVERITY: Warning
FORMAT: "Invalid message type %x, arg %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid IPC ctl message type"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-4-NAMEINVMSGVER

SEVERITY: Error
FORMAT: "Invalid message version %x, arg %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid IPC message Version"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-NAMEENTRYOVRRID

SEVERITY: Warning
FORMAT: "Name entry %s epid %x overriden with epid %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Name entry of an Endpoint Id is overridden by another"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-4-NAMEENTRYINIT

SEVERITY: Error
FORMAT: "Failed to initialize Name Server name entry"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to initialize Name Server name entry"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-NAMEARRAYFULL

SEVERITY: Error
FORMAT: "FIPC Name Server name array is full"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "FIPC name server name array is full"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-NAMEMSGALLCFAIL

SEVERITY: Error
FORMAT: "Failed to allocate BIND/RESOLVE ACK message"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to allocate BIND/RESOLVE ACK message"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-NAMEENTRYBNDINV

SEVERITY: Warning
FORMAT: "Returned name entry %x out of name array bounds %x-%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Returned name entry out of name array boundary"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-NAMENOENTRYOUT

SEVERITY: Warning
FORMAT: "No outstanding name entry %x in name array"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "No outstanding name entry in name array"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-LCNOUTOFRANGE

SEVERITY: Warning
FORMAT: "LCN %d out of range <%d-%d>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "LCN out of range"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-4-LCNALREADYBOUND

SEVERITY: Error
FORMAT: "Bind failed LCN %d already bound by %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Bind failed because LCN already bound by Taskid"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-5-LCNSARREGFAILED

SEVERITY: Warning
FORMAT: "Bind Failed LCN %d failed SAR registration, errno %x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Bind Failed because LCN failed while SAR registration"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-LCNSARUNREGFAIL

SEVERITY: Warning
FORMAT: "Unbind Failed LCN %d failed SAR unregistration, errno %x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Unbind failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-LCNEPIDINVALID

SEVERITY: Warning
FORMAT: "Bind failed LCN %d, epid %x invalid"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Bind failed because LCN's epid is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-LCNOWNERINVALID

SEVERITY: Warning
FORMAT: "LCN %d owned by %x access by non-owner task %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "LCN being accessed by non owner task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-LCNNOTBOUND

SEVERITY: Warning
FORMAT: "LCN %d is not bound"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "LCN not bound"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-LCNMSGSENDERROR

SEVERITY: Warning
FORMAT: "Failed to send msg on LCN %d to epid %x, errno %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to send message on LCN to epid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FIPC-5-CONNREF_INVALID

SEVERITY: Warning
FORMAT: "spiSarLcnGet fail line no %d connRef=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid connection refernce received by SSI IPC"
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

FIPC-4-CONNADD_FAIL

SEVERITY: Error
FORMAT: "spiConnAdd fail line no %d connRef=%d, connType=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "spiConnAdd failed!"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CONNDEL_FAIL

SEVERITY: Error
FORMAT: "spiConnDel fail line no %d connRef=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "spiConnDel failed!"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-LCNBIND_FAIL

SEVERITY: Error
FORMAT: "ssiIpcLcnBind fail line no %d connRef=%d, lcn=%d, epid=0x%x, hanle=0x%x, offset=0x%x, option=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssiIpclcnBind failed!"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-LCNUNBIND_FAIL

SEVERITY: Error
FORMAT: "ssiIpcLcnUnbind fail line no %d connRef=%d, lcn=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssiIpclcnUnbind failed!"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTCSTATETRAFAIL

SEVERITY: Error
FORMAT: "%s - CTC state transition failed, event %x, rc %x, errno %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ctc state transition failed for event"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

FIPC-4-CTCEVTREGFAIL

SEVERITY: Error
FORMAT: "%s - CTC Event Registration failed, event %x, rc %x, errno %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "CTC event registration failed for event"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

DDTS "stats-upload"

STAT-1-FATAL_ERROR

SEVERITY: Fatal
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Fatal Error in Stat File Mgr"
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-MAJOR_ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Major Error in Stat File Mgr. Here are some of the error Failed to enqueue cell for stat, Failed to call other APIs, failed to read/init ram disk and more ...These errors can cause the statistics file upload requests to 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. 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-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Minor Error in Stat File Mgr. Here are some of the error Can not release semaphore Can not take semaphore Unable to resolve EPID IPC send message failed and more .... These errors may not abort the statistics file upload request but need to be logged to aid debugging in case there are other serious problems."
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 Stat File Mgr. Here are some of the warning Can not allocate memory Received unexpected messsage Card event register failure and more ..."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "ssi"

SRAP-4-IOV_NOTFREED

SEVERITY : Error
FORMAT : "Application with SyncRam DBID 0x%x and Receive Handler 0x%x did not free IOV with Mblk 0x%x"
FLAG : No Flag
THROTTLING : No Throttling
EXPLANATION : "Sync RAM Application Error: IOV given to Receive Handler must be freed by application"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO : No Required Info

SRPR-4-INVALID_PDU

SEVERITY: Error
FORMAT: "%s (CONID %p) Invalid PDU - %s = %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error PDU has bad message type or Dup of the PDU message failed"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INVALID_PDUVER

SEVERITY: Error
FORMAT: "%s (CONID %p) received an invalid PDU version %d (%d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error PDU version does not match the SyncRam Message Version"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INVALID_UNBLOCK

SEVERITY: Error
FORMAT: "%s (CONID %x) Failed to unblock the application (%d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Unblock of application failed due to any one of the following failed message allocation, bad block type, failed open on transmit window, failed semaphore give."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-5-INVALID_INIT

SEVERITY: Warning
FORMAT: "Attempt to re-initialize the Sync RAM Update Module"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Attempt to re-initialize the Sync RAM Update Module"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRPR-4-FAILED_CTCCALL

SEVERITY: Error
FORMAT: "%s %s 0x%x %s 0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error failed to successfully complete one of the CTC confirm functions"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INVALID_CTCEVT

SEVERITY: Error
FORMAT: "%s CTC Event (0x%x) is invalid (%s). Current SR Task State=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Received a invalid CTC event or an event unsupported by this module"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INV_CTC_RETVAL

SEVERITY: Error
FORMAT: "%s CTC API (%s) return invalid (0x%x) - %s (0x%x). Current SR Task State=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Received a invalid CTC event or an event unsupported by this module"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INVALID_SM_LOCK

SEVERITY: Error
FORMAT: "%s Can't lock the state machine, taskId=0x%x (errno=0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Take on the Protocol State machine semaphore failed"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-SM_LOCK_TIMEOUT

SEVERITY: Error
FORMAT: "%s Timeout locking the state machine, taskId=0x%x (errno=0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Take on the Protocol State machine semaphore timed out"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INVALID_SMUNLCK

SEVERITY: Error
FORMAT: "%s Can't unlock the state machine, taskId=0x%x (errno=0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Give on the Protocol State machine semaphore failed"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INVALID_BLOCK

SEVERITY: Error
FORMAT: "%s Invalid Applid = 0x%x (expected 0x%x) Current Task=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error The application trying to set the blocking type is not the one that created the connection."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INVALID_DBID

SEVERITY: Error
FORMAT: "%s SyncRam DBID 0x%x is invalid"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Input parameter ssiDbid is invalid"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-5-SR_DBIDWARN

SEVERITY: Warning
FORMAT: "Invalid SyncRam DbId=0x%x is used"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Warning An invalid DbId is used. It should not be used as index to syncRam table."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRPR-5-INVALID_EVENT

SEVERITY: Warning
FORMAT: "%s Invalid Event (%d) for DBID (0x%x) [state=%d]"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error Invalid Event (out of range) or not supported for the current state"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRPR-4-SR_IPCERR

SEVERITY: Error
FORMAT: "%s [%s] failed for DbId=%p by Tid=%x. Errno=%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error IPC api specified returned error"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-INVALID_EVTFUNC

SEVERITY: Error
FORMAT: "%s Invalid Event function (NULL) for ConId(0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error No event function registered for the current ConId but SYNCDONE event is enabled"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRPR-4-SR_NO_RSRC

SEVERITY: Error
FORMAT: "%s Failed allocating resource %s Err=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Failed to allocate resource"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number.
4. do a hot coredump and collect the coredump zip file. "

SRPR-5-SR_IPCWARNING

SEVERITY: Warning
FORMAT: "%s [%s] Message is not in Rxmt Q for DbId=%x by Tid=%x."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Warning Message is either not yet in the Rxmt queue or already removed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRPR-7-SR_SYNCDONE

SEVERITY: Information
FORMAT: "%s %s for ConId 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Informational Indicates whether a message is sent to the APP indicating SYNCDONE or SYNCDONE flag is set so that when the APP calls the ssiRamSyncReceiveReady API, SYNCDONE event is delivered."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRPR-7-ACK_TIMEOUT

SEVERITY: Information
FORMAT: "%s Role=%s CONID=0x%x detects %s %s=%d, %s=%d "
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Timeout for an expected ACK has been detected Peer application did not ACK this message. This application might have been starved out by other higher priority applications."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRPR-5-SR_BADREG

SEVERITY: Warning
FORMAT: "%s %s from Slot=%d for ConId 0x%x communicated with Slot=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Informational Detects a case where a register message is sent from a slot for a DbId that is established to talk to another slot. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "ssi"

SRAP-7-NO_EVENT

SEVERITY: Information
FORMAT: "Later"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-4-API_INVALIDPARM

SEVERITY: Error
FORMAT: "%s Parameter %s has invalid value %x (DBID %x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Sync RAM API Error Input parameter (IOVPtr or index) is invalid (NULL) or exceeds number of elements. It needs to be analyzed by TAC/Development team. In normal operation, such an error should never get report. "
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-5-API_INVALIDPARM

SEVERITY: Warning
FORMAT: "%s Invalid Parameter (%s=0x%x) (%s=0x%x) (DBID %x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Sync RAM API Error Input parameter (IOVPtr or index) is invalid (NULL) or exceeds number of elements"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_DBNAME

SEVERITY: Warning
FORMAT: "%s Invalid DB Name entered (%s)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API Error DB Name exceeds the maximum allowed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_DBID

SEVERITY: Warning
FORMAT: "%s SyncRam DBID 0x%x is invalid"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Sync RAM API Error Input parameter ssiDbid is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_WINSIZE

SEVERITY: Warning
FORMAT: "%s Window size (%d) is invalid, max. allowed Window size is %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API ERROR Window size exceeds the maximum allowed window size"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_RECSIZE

SEVERITY: Warning
FORMAT: "%s Record size (%d) is invalid, max. allowed Record size is %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API ERROR Record size exceeds the maximum allowed record size"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_REREG

SEVERITY: Warning
FORMAT: "%s The connection '%s' is already in use"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API error Input Connection ID has already been registered"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-TOOMANYCONS

SEVERITY: Warning
FORMAT: "%s The Maximum number of connections are allocated (%d)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API error SYNC RAM DB Table is full"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INV_IOVMAXELEMS

SEVERITY: Warning
FORMAT: "%s DBID 0x%x Max Elements in IOV (%d) exceeds max. possible(%d)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API Error Input parameter maxElements exceeds number of elements possible"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-FAILED_BUFALLOC

SEVERITY: Warning
FORMAT: "%s IOV Buffer Allocation failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API error srProtoMsgAllocate() returned NULL"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_IOVSIZE

SEVERITY: Warning
FORMAT: "%s IOV Control Data Size(%d) exceeds max allowed Data len(%d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Sync RAM API error IOV control data exceeds the maximum allowed buffer size for an IOV"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_TID

SEVERITY: Warning
FORMAT: "%s TaskId (0x%x) is invalid"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API error Input parameter TaskID is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INV_APPSTATE

SEVERITY: Warning
FORMAT: "%s Application not in valid state for RamSync DB Registration"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API error Card should not be in READY state for DB registration"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_APICALL

SEVERITY: Warning
FORMAT: "%s Invalid call of API, unexpected %s (0x%x) defined for DBID (%x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API error If EPID Handler is defined, IovReceive API cannot be invoked"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-BAD_RESETACK

SEVERITY: Warning
FORMAT: "%s Bad Call to ssiRamSyncDbResetAck(0x%x) with no pending reset"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Sync RAM API error Bad call to ssiRamSyncDbResetAck() with no pending reset"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_EPID

SEVERITY: Warning
FORMAT: "%s Invalid EPID in DB Table Entry for DBID (%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Sync RAM API error EPID has SSI_INVALID_COM_EPID value, which is not allowed for any DBID."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-4-FAILED_PROTOEVT

SEVERITY: Error
FORMAT: "%s Protocol Event (%d) failed for conId Data transfer API identifier (%p)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Sync RAM API error srProtoEvent() failed for the specific event."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-5-INVALID_FUNC

SEVERITY: Warning
FORMAT: "%s Function is not implemented"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API error Function not implemented In normal operation, such an error should never get report."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_EVTREG

SEVERITY: Warning
FORMAT: "%s Invalid Events (0x%x) being registered (allowed mask=0x%x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Sync RAM API error Invalid Events are being registered"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-IOV_INVLDIOVHDR

SEVERITY: Warning
FORMAT: "%s Invalid IOV Hdr param %s is %x, max %x (DBID %x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Either current buffer number exceeds maximum buffer number or current IOV element exceeds maximum IOV elements"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-IOV_NUMELEMINV

SEVERITY: Warning
FORMAT: "%s DBID %x, Invalid # of elements %d in IOV (Hdr says %d)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Number of elements exceeds the max IOV elements in the header"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-4-IOV_BUFHDRINVLD

SEVERITY: Error
FORMAT: "%s Invalid IOV Buf Hdr DBID %x (%x), BUFNO %x (%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error IOV Buffer header contains either mismatched DB ID or bad transaction buffer number"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-5-IOV_BUFVERINVLD

SEVERITY: Warning
FORMAT: "%s Invalid IOV Buf Hdr DBID %x, VER %x (%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Buffer Version in IOV has unsupported version number"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-IOV_BUFSIZEINV

SEVERITY: Warning
FORMAT: "%s Invalid IOV Buffer Size DBID %x, Size %x (%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Buffer size is less than the space allocated in the message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-IOV_BUFLIMITINV

SEVERITY: Warning
FORMAT: "%s Inv Buf Limit, DBID %x, Limit %x (%x), mbPtr %x, datap %x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error An invalid buffer size limit was reached."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-4-IOV_BUFFERFREE

SEVERITY: Error
FORMAT: "Error freeing buffer %d from IOV Hdr %x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Message free on the buffer failed. More information should be reflected from Ipc message free action. "
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-4-IOV_ELEMDATALEN

SEVERITY: Error
FORMAT: "%s IOV Elem data len %d exceeds max len %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Detects application attempting to add element with a data length which is exceeded the maximum set in the IOV header."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative. This should not get report under normal operation. "
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-5-IOV_ACCFUNCERR

SEVERITY: Warning
FORMAT: "%s DBID %x acc func error, rc %x, errno %x, dataLen %x (%x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Access function failed by either returning an ERROR, or setting actual Data length to 0 or actual data length exceeds the maximum data length"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-4-IOV_NOACCFUNC

SEVERITY: Error
FORMAT: "%s DBID %x has no access function"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error No access function was defined. In normal operation, such an error should never get report."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-4-IOV_ELEMTYPEINV

SEVERITY: Error
FORMAT: "%s DBID %x IOV Element type %x is invalid"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Element type has to be one of DATA or FUNCTION Access, in this case it was invalid. Under normal operation, such an error should never get report. "
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-4-IOV_ELEMBUFFER

SEVERITY: Error
FORMAT: "%s DBID %x IOV Elem Buffer %d out of bounds for IOV (%d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Element buffer number exceeds maximum outstanding records. Under normal operation, such an error should never get report."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-4-IOV_ELEMOFFSET

SEVERITY: Error
FORMAT: "%s DBID %x - IOV Elem Offset %d exceeds buffer %d offset %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Buffer Offset exceeds the maximum data length specified in the header. Under normal operation, such an error should never get report."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-4-IOV_DUPFAILED

SEVERITY: Error
FORMAT: "%s DBID %x - IOV pointer (0x%x) dup failed"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error IOV Pointer duplication failed. IPC resource problem related."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45

SRAP-5-IOV_HDRDUPFAIL

SEVERITY: Warning
FORMAT: "%s DBID %x - MBLK pointer (0x%x) dup failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error MBLK pointer duplication failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-7-IOV_STBY_SEND

SEVERITY: Information
FORMAT: "%s DBID %x - attempts an IOV send from STDBY."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Standby application attempts a limited sending of data to the Active."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-IOV_STBY_SEND_F

SEVERITY: Warning
FORMAT: "%s DBID %x - Blocking Send unsupported on STDBY(TrAck=%d, Tmout=%d)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API IOV Error Standby does not allow blocking send, which would mean no - transaction ack or non-zero timeouts"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-INVALID_EVTFUNC

SEVERITY: Warning
FORMAT: "%s Invalid Event function (NULL) for ConId(0x%x)"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Synchronous Protocol Error No event function registered for the current ConId but SYNCDONE event is enabled"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-2-API_CONV_FUNC_F

SEVERITY: Major Alert
FORMAT: "%s DBID=0x%x peerVer=0x%x transId=0x%x err0x%x failed conversion"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API failed to up/downgrade iov elem ptr In normal operation, such an error should never get report."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
2. Identify the up/downgrade from and to version. "

SRAP-5-API_CONV_MAJ_FA

SEVERITY: Warning
FORMAT: "%s %s <0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to temporary resource or problems which affect a single app during up/downgrade iov elem ptr"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-API_CONV_MAJ_FA

SEVERITY: Warning
FORMAT: "Failed to allocate memory. %s %s <0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to not able to allocate temporary resource which affect a single app during up/downgrade DB"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-API_CONV_MAJ_FA

SEVERITY: Warning
FORMAT: "%s %s <0x%x,0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to temporary resource or problems which affect a single app during up/downgrade iov elem ptr"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-3-API_CONV_MAJ_FA

SEVERITY: Minor Alert
FORMAT: "Failed to allocate memory for new bucket %s %s <0x%x,0x%x,0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to not able to allocate resource which affect a single app during up/downgrade DB registration"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error."

SRAP-5-API_CONV_MAJ_FA

SEVERITY: Warning
FORMAT: "%s %s <0x%x,0x%x,0x%x,0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to temporary resource or problems which affect a single app during up/downgrade iov elem ptr"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-2-API_CONV_FATAL_

SEVERITY: Major Alert
FORMAT: "%s %s <0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to nonrecoverable problems (e.g. corruption ) during up/downgrade iov elem ptr These errors can prevent the task to come up. The errors could be the followings Can not create semaphore during task initialization Can not take semaphore "
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error."

SRAP-2-API_CONV_FATAL_

SEVERITY: Major Alert
FORMAT: "%s %s <0x%x,0x%x>"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to nonrecoverable problems (e.g. corruption ) during up/downgrade iov elem ptr. These errors could be the following Unexepected NULL key that map to the conversion structure. A call to a conversion API call failed."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error."

SRAP-5-API_CONV_FATAL_

SEVERITY: Warning
FORMAT: "Memory corruption. One of the buffer is NULL. %s %s <0x%x,0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Memory corruption. One of the buffer is NULL"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-API_CONV_FATAL_

SEVERITY: Warning
FORMAT: "%s %s <0x%x,0x%x,0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to nonrecoverable problems (e.g. corruption ) during up/downgrade iov elem ptr. The buffer size is zero."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-API_CONV_FATAL_

SEVERITY: Warning
FORMAT: "%s %s <0x%x,0x%x,0x%x,0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API failed due to nonrecoverable problems (e.g. corruption ) during up/downgrade iov elem ptr"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-API_CONV_FAIL

SEVERITY: Warning
FORMAT: "%s %s <0x%x>"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API is used incorrectly "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-API_CONV_FAIL2

SEVERITY: Warning
FORMAT: "%s %s <0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API is used incorrectly"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-2-API_CONV_FAIL3

SEVERITY: Major Alert
FORMAT: "%s %s <0x%x, 0x%x, 0x%x>"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API is used incorrectly"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error."

SRAP-4-API_CONV_FAIL4

SEVERITY: Error
FORMAT: "%s %s <0x%x, 0x%x, 0x%x, 0x%x>"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API is used incorrectly"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-4-API_CONV_FAIL5

SEVERITY: Error
FORMAT: "%s %s <0x%x, 0x%x, 0x%x, 0x%x, 0x%x>"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SyncRam API is used incorrectly"
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

SRAP-5-API_CONV_WARNIN

SEVERITY: Warning
FORMAT: "%s %s <0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API is used incorrectly, but problem is already corrected"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-5-API_CONV_WARNIN

SEVERITY: Warning
FORMAT: "%s %s <0x%x,0x%x>"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SyncRam API is used incorrectly, but problem is already corrected"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRAP-4-IOV_INVLDPTR

SEVERITY: Error
FORMAT: "%s %s(0x%x),%s(%d) "
FLAG: Stack Trace
THROTTLING No Throttling
EXPLANATION: "Null IOV ptr is detected. "
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative."
REQUIRED INFO "On PXM45
1. dspversion
2. dsplog - collection the log over a period of two hours to cover
what has happened before and after this error.
3. dsperr of the specified slot and specified error number. "

DDTS "diskdb"

DB2A-5-DB2API_APPL_ID

SEVERITY: Warning
FORMAT: "Error 0x%x getting Application Id for sending %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API failed to get the Application Id using the SSI API for sending message to DB Client"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_MSG_BUF_

SEVERITY: Warning
FORMAT: "Error 0x%x allocating message buffer for sending %s of length %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API failed to allocate a message buffer using the IPC API."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_MSG_BUF_

SEVERITY: Warning
FORMAT: "Error 0x%x releasing message buffer 0x%x for sending %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API failed to release a message buffer using the IPC API."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_SYN_MSG_

SEVERITY: Warning
FORMAT: "Error 0x%x sending synchronous message of type %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API failed to send the synchronous message using the IPC API"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_MSG_SEND

SEVERITY: Warning
FORMAT: "Error 0x%x sending asynchronous message of type %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API failed to send the asynchronous message using the IPC API"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_WRONG_RE

SEVERITY: Warning
FORMAT: "Received wrong reply from DB Client. Expecting reply type=%d, got %d, expecting ApplId=%d, got %d, expecting Event Group=%d, got %d, expecting Header Version=%d, got %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API received a reply either of wrong message type or with wrong Application Id"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_REPLY

SEVERITY: Warning
FORMAT: "Error 0x%x received from DB Client for %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API reply from the DB Client indicating failure of the DB request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_INVNAME

SEVERITY: Warning
FORMAT: "Invalid %s <%s> received from application for %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API received Database or Table Name that is either not terminated with NULL or longer than allowed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_INVPARAM

SEVERITY: Warning
FORMAT: "Invalid %s <0x%x> received from application for %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API received invalid parameter as inidicated in specified operation."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_INVPTR

SEVERITY: Warning
FORMAT: "%s <0x%x> received from application for %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API received invalid pointer parameter as indicated in specified operation."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_INV_LSLO

SEVERITY: Warning
FORMAT: "Invalid Logical slot=%d received from applId=%d for <%s>"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API received invalid logical slot number for the operation specified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_INV_SVR_

SEVERITY: Warning
FORMAT: "Invalid Server Command=%d received from application for %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API received invalid Server Command from the application"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-5-DB2API_INV_SVR_

SEVERITY: Warning
FORMAT: "Invalid Server Type=%d received from application for %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "DB Client API received invalid Server Type from the application"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-7-STBYRDENABLE

SEVERITY: Information
FORMAT: "Application requested to enable DB Reads on Standby"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "The calling application requested to enable DB Reads on Standby PXM."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-7-STBYRDDISABLE

SEVERITY: Information
FORMAT: "Application requested to disable DB Reads on Standby"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "The calling application requested to disable DB Reads on Standby PXM."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DB2A-7-REG

SEVERITY: Information
FORMAT: "Registration %s request received for lslot=%d"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "The calling application indicates that the registration for the specified slot begins or ends as specified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "ssi"

SSI-2-MAJOR_ERROR

SEVERITY: Major Alert
FORMAT: "Where %s()%d, Errno 0x%x, ErrMsg %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SSI major error func()line, Errno, Error Msg"
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-ERROR_STKYES

SEVERITY: Warning
FORMAT: "Where %s()%d, Errno 0x%x, ErrMsg %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SSI error with stk trace func()line, Errno, Error Msg"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-ERROR_STKNO

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

SSI-4-PARMINVALID

SEVERITY : Error
FORMAT : "%s, line %d, Invalid parameter %s address %x"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Parameter invalid"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-PARMMAXEXCEEDED

SEVERITY: Error
FORMAT: "Parm %s '%d' has exceeded max %d to %s."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function exceeded maximum value specified."
RECOMMENDED ACTION: "Look for the events logged by the module/function calling the specified API function and take the actions recommended for those events."
REQUIRED INFO "Collect the event and error logs."

SSI-4-PARMOUTOFRANGE

SEVERITY : Error
FORMAT : "%s, line %d, Invalid parameter %s, value %d"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Parameter out of range"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.
l

SSI-4-TASKENTRYGETFAI

SEVERITY : Error
FORMAT : "%s, line %d, Error getting task entry for task %d"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Error getting task entry"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-TASKIDINVALID

SEVERITY : Error
FORMAT : "%s, line %d, An invalid SSI_TID of %x was passed as an argument"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Invalid Task Id"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-TASKSEMINVL

SEVERITY : Error
FORMAT : "%s, line %d, Invalid Task semaphore errno %x"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Invalid Task semaphore"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-TASKSEMTAKE

SEVERITY : Error
FORMAT : "%s, line %d, Error taking Task semaphore for task %d, errno %x"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Error acquiring Task semaphore"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-TASKSEMGIVE

SEVERITY : Error
FORMAT : "%s, line %d, Error giving Task semaphore for task %d, errno %x"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Error giving Task semaphore"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-TASKSEMCREATE

SEVERITY : Error
FORMAT : "%s, line %d, Error creating Task semaphore for task %d, errno %x"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Error creating Task semaphore"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-TASKSEMDEL

SEVERITY : Error
FORMAT : "%s, line %d, Error deleting Task semaphore for task %d, errno %x"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Error deleting Task semaphore"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-TIMERERROR

SEVERITY : Error
FORMAT : "%s, line %d, Error processing timer"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Error Processing Timer"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-TIMEREVENT

SEVERITY : Error
FORMAT : "%s, line %d, task %d, timeout %d"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Process timed out waiting for a message"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-4-CHUNKINVPTR

SEVERITY : Error
FORMAT : "%s, line %d, The chunk pointer is invalid"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "A bad or NULL Chunk pointer was passed"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SSI-6-RESETDUMPTRACE

SEVERITY: Notice
FORMAT: "A function trace dump is available from the last reset."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A function trace dump has been saved which contains a trace of the operations being done before the current reset. If the reset was a watchdog timeout then this information will indicate what was happening when the watchdog occurred."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-3-EXCEPTION

SEVERITY: Minor Alert
FORMAT: "Software Exception Vector %d EPC 0x%08x ADDR 0x%08x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A software exception has occurred. The vector number specifies the type of exception. The EPC is the program counter of the failing instruction. The address field is the address that was attempted to be accessed if a load or store TLB or Address exception. See the associated error log for additional information of the exception state."
RECOMMENDED ACTION: "The software automatically takes the configured recovery action. The recovery actions are configured depending on the module that has taken the exception. If the card on which the exception occurred is not reset, check the status of the card using the command to display the cards' status. If the display indicates that the card is in FAILED state, the module that has taken the exception is no longer available to provide the module's functionality and hence, the card is in degraded mode. In this situation the card doesn't have its redundancy available. Try to bring up its redundant card. If the its Standby successfully comes up, there will be an automatic switchover to the healthy Standby. If its redundancy could not be brought up, then, the card that is in FAILED state should be reset to recover from the failure."
REQUIRED INFO "If the card was reset automatically, core may have been dumped on the hard disk of the Active controller card. If the core was dumped, collect the core. If the card was not reset, call TAC to reset the card in such a way that core would be dumped. Collect the event and error logs."

SSI-4-ISRNOTCALLABLE

SEVERITY: Error
FORMAT: "Function %s cannot be called by Interrupt Service Routine."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The named function was called by an interrupt service routine and it cannot perform any blocking function calls. The consequences of this error depend on the function that was called and ISR that called the function."
RECOMMENDED ACTION: "Report the error to TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-ISRNOTCLBLEPC

SEVERITY: Error
FORMAT: "At PC 0x%x Function %s called by ISR."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The named function was called by an interrupt service routine at specified PC and it cannot perform any blocking function calls. The consequences of this error depend on the function that was called and ISR that called the fu nction."
RECOMMENDED ACTION: "Report the error to TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TBLSEMTAKEFAIL

SEVERITY: Error
FORMAT: "Unable to take Vx semaphore %p protecting %s table. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The VxWorks semaphore used to protect the specified system table was not able to be taken. SSI may not be initialize properly or it could be due to memory corruption. The result of this error depends on the function that was being performed."
RECOMMENDED ACTION: "Look for events logged subsequent to this event to determine the consequences of this event. If this error occurred on an Active card, try to switchover. If this error occurred on a Standby card, reset the Standby card."
REQUIRED INFO "If this event was logged on a controller card, take a hot-dump of the core. If this event was logged for a Service Module, call TAC to take the core dump while resetting. Collect event and error logs."

SSI-5-OBJCREATENOMEM

SEVERITY: Warning
FORMAT: "%s creation failed due to memory shortage in VxWorks partition."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Creation of a VxWorks object failed due to a memory shortage in the VxWorks system memory partition."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SSI-5-SEMTBLFULL

SEVERITY: Warning
FORMAT: "The system semaphore table is full. All %d entries are used."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The system semaphore table is full. There are no more entries available to create a SSI_SEMID. The system limit needs to be increased or dynamically created semaphores are not being deleted."
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

SSI-4-SEMDAINVALID

SEVERITY: Error
FORMAT: "Deadlock action %d is invalid to create SSI semaphore."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid deadlock action value was passed in as an argument to create a SSI semaphore."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-SEMTYPEINVALID

SEVERITY: Error
FORMAT: "Sem Type %d is invalid to create SSI semaphore."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid semaphore type value was passed in as an argument to create a SSI semaphore."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-SEMOPTINVALID

SEVERITY: Error
FORMAT: "Sem Option %d is invalid to create SSI semaphore of type %d."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid semaphore option value was passed in as an argument to create a SSI semaphore."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-SEMSTATEINVALID

SEVERITY: Error
FORMAT: "Sem Initial State %d is invalid to create SSI semaphore."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid semaphore initial state value was passed in as an argument to create a SSI semaphore."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-SEMCREATEFAIL

SEVERITY: Warning
FORMAT: "Semaphore creation failed. Errno=%x."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Creation of a semaphore failed unexpectedly."
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

SSI-4-SEMIDINVALID

SEVERITY: Error
FORMAT: "An invalid SSI_SEMID of %p was passed as an argument."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid SSI semaphore id was passed in as an argument into the function. The SSI_SEMID is in the incorrect format."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-SEMIDDELETED

SEVERITY: Warning
FORMAT: "SSI_SEMID %p was deleted and no longer exists."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI semaphore id that was passed in as an argument is no longer valid. The SSI_SEMID probably has been deleted."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-5-SEMDELUNOWN

SEVERITY: Warning
FORMAT: "SSI_SEMID %p is being deleted and is owned by another task %p."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI semaphore id that is being deleted is not owned by the deleting task and could be owned by another task. A mutual exclusion semaphore should be taken before deletion."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-4-SEMDELFAIL

SEVERITY: Error
FORMAT: "Delete of semaphore %p for SSI_SEMID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The deletion of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly. Memory resources may have been lost."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-SEMTAKEFAIL

SEVERITY: Error
FORMAT: "Take of semaphore %p for SSI_SEMID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The Take of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly. This could be due to memory corruption."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-SEMGIVEUNOWN

SEVERITY: Error
FORMAT: "SSI_SEMID %p is not owned by giving task. It is owned by task %p."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The SSI semaphore id that is being given is not owned by the giving task and mutual exclusion semaphore can only be given by the owning task."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-SEMGIVEFAIL

SEVERITY: Error
FORMAT: "Give of semaphore %p for SSI_SEMID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The Give of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly. This could be due to memory corruption."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-SEMFLUSHINV

SEVERITY: Error
FORMAT: "SSI_SEMID %p cannot be flushed - operation invalid."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The SSI semaphore id that is being flushed does not support the flush operation and should not be called."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-SEMFLUSHFAIL

SEVERITY: Error
FORMAT: "Flush of semaphore %p for SSI_SEMID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The Give of VxWorks semaphore used to implement the SSI_SEMID failed unexpectedly. This could be due to memory corruption."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-MQTBLFULL

SEVERITY: Warning
FORMAT: "The system message queue table is full. All %d entries are used."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The system message queue table is full. There are no more entries available to create a SSI_MQID. The system limit needs to be increased or dynamically created message queues are not being deleted."
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

SSI-4-MQMAXINVALID

SEVERITY: Error
FORMAT: "Max messages value %d is invalid to create SSI message queue."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid maximum number messages in the message queue was passed in as an argument to create a SSI message queue."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-MQMLENINVALID

SEVERITY: Error
FORMAT: "Message length %d is invalid to create SSI message queue."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid message length value was passed in as an argument to create a SSI message queue."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-MQOWNERINVALID

SEVERITY: Error
FORMAT: "Owning Task %p is invalid to create SSI message queue."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid owner task id value was passed in as an argument to create a SSI message queue."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-MQOWNERNOTEXIST

SEVERITY: Error
FORMAT: "Owning Task %p does not exist to own created SSI message queue."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An non existent owner task id value was passed in as an argument to create a SSI message queue."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-MQCREATEFAIL

SEVERITY: Warning
FORMAT: "Message Queue creation failed. Errno=%x."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Creation of a message queue failed unexpectedly."
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

SSI-5-MQSEMCRTFAIL

SEVERITY: Warning
FORMAT: "Creation of sync semaphore for SSI_MQID failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The creation of VxWorks semaphore used to synchronize multiple SSI_MQID message queues failed unexpectedly."
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

SSI-5-MQIDINVALID

SEVERITY: Warning
FORMAT: "An invalid SSI_MQID of %p was passed as an argument."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An invalid SSI message queue id was passed in as an argument into the function. The SSI_MQID is in the incorrect format."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SSI-5-MQIDDELETED

SEVERITY: Warning
FORMAT: "SSI_MQID %p was deleted and no longer exists."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI message queue id that was passed in as an argument is no longer valid. The SSI_MQID probably has been deleted."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-4-MQQUOTAINVALID

SEVERITY: Error
FORMAT: "Message queue quota value %d is invalid for SSI_MQID %p."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid message queue quota value was passed in as an argument to set the quota on a SSI message queue."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-MQSEMDELFAIL

SEVERITY: Error
FORMAT: "Delete of sync semaphore %p for SSI_MQID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The deletion of VxWorks semaphore used to synchronize multiple SSI_MQID message queues failed unexpectedly. Memory resources may have been lost."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MQDELFAIL

SEVERITY: Error
FORMAT: "Delete of message queue %p for SSI_MQID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The deletion of VxWorks message queue used to implement the SSI_MQID failed unexpectedly. Memory resources may have been lost."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MQFLSHRECVFAIL

SEVERITY: Error
FORMAT: "Receive to flush Vx Message Queue %p failed. Errno=%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The receive on the VxWorks message queue to flush it failed unexpectedly. It could have been corrupted or deleted unexpectedly"
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MQSENDLENINV

SEVERITY: Error
FORMAT: "Message length of %d to send to SSI_MQID %p is invalid."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid message length value was passed in as an argument to send message to a SSI message queue."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-MQSENDFAIL

SEVERITY: Error
FORMAT: "Send to Vx msgQ %p for SSI_MQID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The send to VxWorks message queue used to implement the SSI_MQID failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MQSEMGIVEFAIL

SEVERITY: Error
FORMAT: "Give of sync semaphore %p for SSI_MQID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The give of VxWorks semaphore used to synchronize multiple SSI_MQID message queues failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MQISRSENDNZTO

SEVERITY: Error
FORMAT: "Send to SSI_MQID %p was done with timeout %d by ISR."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The send to message queue was done by an Interrupt Service Routine with a non zero timeout value. ISRs cannot block."
RECOMMENDED ACTION: "Report the error to TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-MQRECVLENINV

SEVERITY: Error
FORMAT: "Message length of %d to receive from SSI_MQID %p is invalid."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid message length value was passed in as an argument to receive message from a SSI message queue."
RECOMMENDED ACTION: "Report the error to TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-MQRECVFAIL

SEVERITY: Error
FORMAT: "Receive from Vx msgQ %p for SSI_MQID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The receive from VxWorks message queue used to implement the SSI_MQID failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MQSEMTAKEFAIL

SEVERITY: Error
FORMAT: "Take of sync semaphore %p for SSI_TID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The give of VxWorks semaphore used to synchronize multiple SSI_MQID message queues failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MQHNDLRINVALID

SEVERITY: Error
FORMAT: "Msg Handler %p is invalid to process msg for SSI_MQID %p."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An invalid message handler function pointer value was passed in as an argument to create a SSI message queue that requires a message handler."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-MQHNDLRFAIL

SEVERITY: Warning
FORMAT: "Msg Handler %p failed processing msg for SSI_MQID %p. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The message handler function returned failure while processing a message received in the SSI message queue."
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

SSI-4-MQNUMMSGFAIL

SEVERITY: Error
FORMAT: "Get num of msg in Vx msgQ %p for SSI_MQID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Getting the number of messages in the VxWorks message queue used to implement the SSI_MQID failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MQINFOPTRINV

SEVERITY: Error
FORMAT: "Msg Info Ptr %p is invalid to get info SSI_MQID %p."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid message info structure pointer value was passed in as an argument to get SSI message queue information."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-MQINFOFAIL

SEVERITY: Error
FORMAT: "Get info about Vx msgQ %p for SSI_MQID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Getting the information about the VxWorks message queue used to implement the SSI_MQID failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-TASKTBLFULL

SEVERITY: Warning
FORMAT: "The system task table is full. All %d entries are used."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The system task table is full. There are no more entries available to create a SSI_TID. The system limit needs to be increased or dynamically created tasks are not being deleted."
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

SSI-4-TASKSEMGIVEFAIL

SEVERITY: Error
FORMAT: "Give of sync semaphore %p for SSI_TID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The give of VxWorks semaphore used to synchronize child SSI_TID initialization status with spawning parent failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-TASKINITPTO

SEVERITY: Warning
FORMAT: "SSI_TID %p unable to send init status because parent timed-out."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The child SSI_TID was unable to send its initialization status to the spawning parent task as the parent timed-out and is no longer waiting for the child status."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-5-TASKINITFAIL

SEVERITY: Warning
FORMAT: "SSI_TID %p initialization failed. Errno=%x - Task suspended."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI_TID failed to initialize properly and was suspended to prevent further errors."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-4-TASKIDINVALID

SEVERITY: Error
FORMAT: "An invalid SSI_TID of %p was passed as an argument."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid SSI task id was passed in as an argument into the function. The SSI_TID is in the incorrect format."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-TASKIDDELETED

SEVERITY: Warning
FORMAT: "SSI_TID %p was deleted and no longer exists."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI task id that was passed in as an argument is no longer valid. The SSI_TID probably has been deleted."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-4-TASKDELFAIL

SEVERITY: Error
FORMAT: "Delete of task %p for SSI_TID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The deletion of VxWorks task used to implement the SSI_TID failed unexpectedly. Memory resources may have been lost."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-TASKDELSAFE

SEVERITY: Warning
FORMAT: "SSI_TID %p is safe from deletion and is suspended."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI task id that was passed in as an argument is safe from being deleted and it is also suspended. Task may have suspended on an exception after taking a task safe mutual exclusion semaphore. Call to delete task is failed rather than cause hang condition to caller."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-5-TASKFORCEDESTRO

SEVERITY: Warning
FORMAT: "task destroy forced tid=0x%x caller=0x%x safeCnt=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A task was destroyed regardless whether it was delete safe or not. It should be exceptional to do so. Deleting a task which is delete safe is potentially dangerous so it should only be done when there is no other choice."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-4-TASKRESUMEFAIL

SEVERITY: Error
FORMAT: "Resume of task %p for SSI_TID %p failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The resumption 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."

SSI-4-TASKSUSPENDFAIL

SEVERITY: Error
FORMAT: "Suspend of task %p for SSI_TID %p failed. Errno=%x"
FLAG: No Flag
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."

SSI-5-TASKSUSPENDSAFE

SEVERITY: Warning
FORMAT: "SSI_TID %p is safe from deletion could be holding semaphores."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI task id that was passed in as an argument is safe from being deleted. The task may be holding a mutual exclusion semaphore and should not be suspended. Suspension could result in a deadlock of the system. Suspension is failed rather than cause hang condition to system."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-4-TASKRESTARTFAIL

SEVERITY: Error
FORMAT: "Restart of task %p for SSI_TID %p failed to %s. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The restart 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."

SSI-4-TASKPRIOINVALID

SEVERITY: Error
FORMAT: "Task priority value %d is invalid to create SSI task."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid task priority number was passed in as an argument to create a SSI task."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TASKPGRPINVALID

SEVERITY: Error
FORMAT: "Task priority group %d is invalid to create SSI task."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid task priority group was passed in as an argument to create a SSI task."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TASKAPPLINVALID

SEVERITY: Error
FORMAT: "Task application id value %d is invalid to create SSI task."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid task application id value was passed in as an argument to create a SSI task."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TASKSTKSIZEINV

SEVERITY: Error
FORMAT: "Task stack size value %d is invalid to create SSI task."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid task stack size value was passed in as an argument to create a SSI task."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TASKSUSPACTINV

SEVERITY: Error
FORMAT: "Task suspended action value %d is invalid to create SSI task."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid task suspend action value was passed in as an argument to create a SSI task."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TASKFAILACTINV

SEVERITY: Error
FORMAT: "Task fail action value %d is invalid to create SSI task."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An invalid task fail action value was passed in as an argument to create a SSI task."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-TASKSEMCRTFAIL

SEVERITY: Warning
FORMAT: "Creation of sync semaphore for SSI_TID failed. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The creation of VxWorks semaphore used to synchronize SSI_TID initialization with parent failed unexpectedly."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-TASKSPAWNFAIL

SEVERITY: Warning
FORMAT: "Task spawn failed. Errno=%x."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Spawning of a task failed unexpectedly."
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

SSI-5-TASKINITACKTO

SEVERITY: Warning
FORMAT: "SSI_TID %p timed out initialization of child SSI_TID %p."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The parent SSI_TID timed out the send of initialization status from the child task. Either child task had problems or didn't wait long enough."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-4-TASKWACKFAIL

SEVERITY: Error
FORMAT: "Failed to wait for init status from child SSI_TID %p. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The parent SSI_TID was unable to wait for the send of initialization status from the child task."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-TASKDELMQOWN

SEVERITY: Warning
FORMAT: "SSI_TID %p is being deleted and still owns message queues."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI task id that is being deleted still owns message queues. These message queues should be deleted before the task is deleted if the task is not being recovered."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-4-INVPPARTPTR

SEVERITY: Error
FORMAT: "The private partition structure has not been allocated."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The private partition structure which holds information about the partitions has not been allocated. This indicates a software problem (ssiMemPartInit has not been called, or the pointer has been overwritten)."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-THREEPART

SEVERITY: Error
FORMAT: "Attempted to create %d partitions (only 3 allowed)."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An attempt was made to create an invalid number of partitions. This indicates a software problem."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-MALLOC

SEVERITY: Warning
FORMAT: "Could not create partition info structure (errno %d)."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An error was returned by malloc when attempting to allocate the partition info structure."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SSI-5-NOSEMAPHORE

SEVERITY: Warning
FORMAT: "Could not create a semaphore to partition %d (errno %d)."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An error was returned by semBCreate when attempting to create a semaphore."
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

SSI-4-INVTYPE

SEVERITY: Error
FORMAT: "The requested memory type is invalid %d."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An attempt was made to allocate memory with a memory type parameter that is invalid. This indicates a software problem"
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-INVOPTION

SEVERITY: Error
FORMAT: "The requested options flag is invalid %d."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An attempt was made to allocate memory with an options flag parameter that is invalid. This indicates a software problem."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-ZEROSIZE

SEVERITY: Error
FORMAT: "A request for 0 bytes was made."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An attempt was made to allocate 0 bytes. This indicates a software problem."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-INVLENGTH

SEVERITY: Error
FORMAT: "The requested length %d is greater than partition 0x%x size %d."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An attempt was made to allocate more memory than what is allocated for the partition."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-BELOWTHRES

SEVERITY: Warning
FORMAT: "The number of free bytes %d is below the set threshold %d for partition %d."
FLAG: Stack Trace
THROTTLING One Second
EXPLANATION: "While attempting to allocate low priority memory, the number of free bytes is below the set threshold."
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

SSI-6-CROSSTHRES

SEVERITY: Notice
FORMAT: "Memory Partition %d crossed %s threshold of %d bytes. State %s"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "The memory partition specified has crossed a a threshold value that generates events to applications. The resulting state is indicated."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-5-NOPARTITION

SEVERITY: Warning
FORMAT: "Could not allocate %d bytes from partition 0x%x (errno %d)."
FLAG: Stack Trace
THROTTLING One Second
EXPLANATION: "An error was returned by memPartAlloc while attempting to allocate memory."
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

SSI-5-NOTOWNER

SEVERITY: Warning
FORMAT: "Task %s(0x%x) is not the owner of block 0x%x. Owner=%s(0x%0x)"
FLAG: Stack Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "A process that is not the owner of allocated memory is attempting to deallocate the memory. This indicates a software 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

SSI-5-FREESTATICWARN

SEVERITY: Warning
FORMAT: "Static Memory allocated by Task %s(0x%x) at 0x%x is being freed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A process that is not the owner of allocated memory is attempting to deallocate the memory. This indicates a software 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

SSI-5-MEMPARTCREATE

SEVERITY: Warning
FORMAT: "An error was returned trying to create the partition 0x%x (errno %d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An error was returned by memPartCreate while attempting to create the specified partition."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SSI-5-MEMPARTFREE

SEVERITY: Warning
FORMAT: "An error was returned trying to deallocate memory block at 0x%x (errno %d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An error was returned by memPartFree while attempting to deallocate memory."
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

SSI-4-MEMBLKERROR

SEVERITY: Error
FORMAT: "Memory Block Error %s value 0x%x block %p in %s."
FLAG: Stack Trace | Run Log Function
THROTTLING No Throttling
EXPLANATION: "The memory check routine has found an error as described in the message."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-STRANGEADDR

SEVERITY: Error
FORMAT: "The memory address 0x%x is not within any of the partitions."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The memory address is not within any of the partitions. This indicates a bad address or possible corruption of the memory partition structure."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-CKINVWRDADD2

SEVERITY: Error
FORMAT: "Invalid memory block address 0x%x (not on a word boundary)."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The memory block address is not on a word boundary"
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-INVMEMTYPE

SEVERITY: Error
FORMAT: "Invalid memory type %d for memory block at 0x%x."
FLAG: Dump Trace | Stack Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The memory type stored in the header of the block is wrong. This indicates that the header has been corrupted or is invalid."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-INVLENGTH1

SEVERITY: Error
FORMAT: "Invalid length for memory block at 0x%x owner 0x%x caller 0x%x."
FLAG: Stack Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The length stored by VxWorks is wrong. This indicates that memory has been corrupted."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-INVMAGICCOOKIE

SEVERITY: Error
FORMAT: "Invalid magic number 0x%x for memory block at 0x%x owner 0x%x caller 0x%x."
FLAG: Stack Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The magic number stored at the end of the block is wrong. This indicates that memory has been corrupted."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-INVREFCOUNT

SEVERITY: Error
FORMAT: "Memory block at 0x%x is not allocated (reference count = 0)"
FLAG: Stack Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The reference count for the block is 0. This indicates that the block has already been freed."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-INVVXWORKPART

SEVERITY: Error
FORMAT: "Invalid partition index %d for memory block at 0x%x"
FLAG: Stack Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The partition index in the header is invalid. This block was allocated from the VxWorks memory heap and this should be \"ab1ebeef\". This indicates that the header has been corrupted or is invalid."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-INVPARTINDEX

SEVERITY: Error
FORMAT: "Invalid partition index %d for memory block at 0x%x"
FLAG: Stack Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The partition index in the header is invalid. This indicates that the header has been corrupted or is invalid."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-DOWNSTATIC

SEVERITY: Warning
FORMAT: "Not enought memory in the dynamic pool for %d bytes, trying static"
FLAG: Stack Trace
THROTTLING One Second
EXPLANATION: "The dynamic partition does not have enough space to allocate the specified number of bytes. The software will try to allocate the the space from the static partition."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SSI-5-DOWNVXWORKS

SEVERITY: Warning
FORMAT: "Not enought memory in the static pool for %d bytes, trying VxWorks' heap"
FLAG: Stack Trace
THROTTLING One Second
EXPLANATION: "The static partition does not have enough space to allocate the specified number of bytes. The software will try to allocate the the space from the VxWorks heap."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SSI-4-INVPARTADDR

SEVERITY: Error
FORMAT: "Invalid address 0x%x for partition %d (start0x%x length0x%x)"
FLAG: Stack Trace | Run Log Function
THROTTLING One Tick
EXPLANATION: "The address is not within the range of the partition stored in the header. This indicates that the header has been corrupted or is invalid."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-CHECKFREEBLOCK

SEVERITY: Warning
FORMAT: "FREEBLOCK Overwritten. Part %d Block %x Addr %x (%x %x)."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The unused section of a block on the freeQ was over-written. Somebody has a rogue pointer."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSI-5-FILLCHECKSEMFAI

SEVERITY: Warning
FORMAT: "Fill Check Mode - Take Semaphore Failure. Check Mode Disabled."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The memory fill check system could not take the semaphore, Fill Check mode turned off."
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

SSI-5-TIMERTBLFULL

SEVERITY: Warning
FORMAT: "The system timer table is full. All %d entries are used."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The system timer table is full. There are no more entries available to create a SSI_TIMERID. The system limit needs to be increased or dynamically created tasks are not being deleted."
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

SSI-4-TIMERHANDLER

SEVERITY: Error
FORMAT: "Attempt to create a system timer with invalid handler."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt was made to create a system timer with an invalid handler function."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERNOCREATE

SEVERITY: Error
FORMAT: "Unable to create Vx POSIX timer. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to create a Vx POSIX timer failed. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERNOCONNECT

SEVERITY: Error
FORMAT: "Unable to connect handler function to Vx POSIX timer. Errno=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to create a Vx POSIX timer failed. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERNOCANCEL

SEVERITY: Error
FORMAT: "Unable to cancel Vx POSIX timer. Vx Timer=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to cancel a Vx POSIX timer failed. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERNODELETE

SEVERITY: Error
FORMAT: "Unable to delete Vx POSIX timer. Vx Timer=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to delete a Vx POSIX timer failed. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERINVALIDID

SEVERITY: Error
FORMAT: "SSI function called with invalid ID. SSI Timer=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An ssi function was called with an invalid timer ID. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERINVALIDENT

SEVERITY: Error
FORMAT: "SSI function called with invalid entry. SSI Timer=%x Vx Timer=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An ssi function was called for an invalid timer entry. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERINVALIDTSK

SEVERITY: Error
FORMAT: "Attempt to manipulate timer by non-owning task. SSI Timer=%x Task=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An ssi function was called to operate on a timer entry by a non-owning task. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERINVALIDVAL

SEVERITY: Error
FORMAT: "Function called with invalid time value. Time val=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An ssi function was called with an invalid timer value. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERNOSETGET

SEVERITY: Error
FORMAT: "An attempt to set or get a timer value failed. Time val=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An ssi function call to either set or get the. timer value failed. ssi timers may not be initialize properly."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-TIMERSIGERROR

SEVERITY: Error
FORMAT: "An attempt to manipulate a signal failed. SSI Timer=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An ssi function call to manipulate a POSIX. signal failed. this indicates corruption has occurred."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-TIMERINVTOD

SEVERITY: Error
FORMAT: "An attempt to read the system time-of-day failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The function call to get the current time-of-day failed. this indicates corruption has occurred."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-MKTIMEFAIL

SEVERITY: Error
FORMAT: "Mktime failed in %s. errno=%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The function call to mktime to convert a broken down time to an integer second count failed with the error code specified."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-PUTENVFAIL

SEVERITY: Error
FORMAT: "Putenv of string '%s' failed in %s. errno=%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The function call to putenv to put a variable into the environment failed with the error code specified."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-WDALRCRT

SEVERITY: Error
FORMAT: "%s Watchdog already created, watchdog Id = %x."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The watchdog timer has already been created for Sync Timer usage for the task."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-WDCREATEFAIL

SEVERITY: Error
FORMAT: "SSI %s watchdog create failed in %s. errno=%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unable to create the specified watchdog for the specified use in the named function. It failed with the specified error number."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-WDSTARTFAIL

SEVERITY: Error
FORMAT: "SSI %s watchdog start failed in %s. rc=%d errno=%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unable to start the specified watchdog for the specified use in the named function. It failed with the specified return code and error number."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-5-TMRCANCELINV

SEVERITY: Warning
FORMAT: "SSI Timeout event not found TmoFunc=%p key=%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The specified timeout event could not be found in the named function. The value of the Timeout function and key 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

SSI-4-TMRNOTINIT

SEVERITY: Error
FORMAT: "SSI Sync Timer not initialized for Task %p"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The synchronous timeout facility was not initialized for the calling task before it tried to call the specified function. Initialization must be called before calling the function."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-TMRHNDLRFAIL

SEVERITY: Warning
FORMAT: "Sync Timeout Handler %p failed key=%x rc=%d errno=%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The specified timeout handler function failed in the specified function. It was passed the specified key. The function failed with the specified return code and error number."
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

SSI-5-TMRKEYNOTUNIQ

SEVERITY: Warning
FORMAT: "Timer key/function %d/%p not unique, caller=0x%x"
FLAG: No Flag
THROTTLING Three Minutes
EXPLANATION: "The same combination of timer key and function was found at least twice in the the sync timer linked list. This is an API error, caller must have added a key/function timer which 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. 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

SSI-5-POP1HDRERROR

SEVERITY: Warning
FORMAT: "Popeye 1 message header error buffer=%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A function call to create or access a Popeye 1 message header failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-IPCMSGERROR

SEVERITY: Warning
FORMAT: "An IPC message alloc or free failed buffer=%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A function call to either allocate or free an IPC message buffer failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-POP1TRLERROR

SEVERITY: Warning
FORMAT: "A frame trailer check failed buffer=%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A check of the frame buffer trailer space requirements failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-SSISARTXERROR

SEVERITY: Warning
FORMAT: "A SAR frame or cell transmit failed buffer=0x%x, glcn=%d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to transmit a frame or cell failed in the underlying SAR driver."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-CTCSENDMSGERROR

SEVERITY: Warning
FORMAT: "CTC event generate message failure."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An event generate message sent to CTC failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-EVENTGENERROR

SEVERITY: Warning
FORMAT: "Event generate message failure."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An event generate message from SSI failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-THRESHSETERROR

SEVERITY: Warning
FORMAT: "Thresholds Set failure."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Threshold setting for Memory Chunk failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-4-INVALIDTHRESHID

SEVERITY: Error
FORMAT: "Threshold Values Invalid"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid Threshold Percentage Values Entered."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-STRTOOLONG

SEVERITY: Error
FORMAT: "%s Source String longer than Dest Buffer Size = %d, Src Str ptr = %p."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Internal software error - attempt to copy a string into a buffer that is too short for it"
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-APIERROR

SEVERITY: Error
FORMAT: "%s %s failed, errno=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Internal software error when called an specified API"
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-DOSFAIL

SEVERITY: Warning
FORMAT: "%s WARNING %s, errno=0x%x, File Name=%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Call to specified DOS API 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

SSI-5-DOSWRITEFAIL

SEVERITY: Warning
FORMAT: "Failed for %s, %s, Written= %d, To write= %d(%d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Call to specified DOS API to write to file failed"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SSI-5-DOSFAIL1

SEVERITY: Warning
FORMAT: "%s WARNING %s, errno=0x%x, DIR Pointer=%p"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Call to specified DOS API 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

SSI-4-INTERNALFAIL

SEVERITY: Error
FORMAT: "%s Failed %s 0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Internal software failure while performing specified task"
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-SEMFAIL

SEVERITY: Error
FORMAT: "%s %s, SSI Sem Id=0x%x, errno=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Internal software failure while performing specified task"
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-FILENOTOPEN

SEVERITY: Error
FORMAT: "%s File specified by File Desc=0x%x not opened"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The file specified by the given file descriptor not opened"
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-4-FDCORRUPT

SEVERITY: Error
FORMAT: "%s File Desc=0x%x (%s) was corrupted"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The file specified by the given file descriptor could not be properly invalidated."
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-APPNOTOWNER

SEVERITY: Error
FORMAT: "%s Calling APPL 0x%x is not owner for file %s, owner APPL=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The caller APP is not the owner of the file it is trying to access."
RECOMMENDED ACTION: "Look for the events logged subsequent to this event and take the actions recommended for those events. Report the error the TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-DIO_GEN_ERROR

SEVERITY: Warning
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The DIO module encounter an error for which we want the flexibility to log any string."
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

SSI-5-DIO_DIRCPY_ERRO

SEVERITY: Warning
FORMAT: "There is an error in function %s at line no %d because of %s \n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: " There are some errors like destination & source file(dir) names are same , there also no source dir(file) exist while dir copying"
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

SSI-4-STKCHK

SEVERITY: Error
FORMAT: "Stack usage exceeds threshold (%d percent) Task=%s (0x%x), Size=%d, Usage=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The stack usage for the specified task exceeds the specified threshold. The threshold and the size configured for the task are as specified"
RECOMMENDED ACTION: "Report the error to TAC."
REQUIRED INFO "Collect event and error logs."

SSI-5-SSITRACEDROP

SEVERITY: Warning
FORMAT: "Invalid parameters pass in!!!Max par=4, Cur. par=%d, Module=%s, Format string=(%s)"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "Wrong number of parameters are passed in to the SSI_TRACE api. The current maximum parameters that can be pass in are 4"
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

SSI-1-TEXTCORR

SEVERITY: Fatal
FORMAT: "Code CorruptedStart=0x%x, Size=0x%x, Checksum=0x%x, Stored Checksum=0x%x"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "The code segment was corrupted."
RECOMMENDED ACTION: "Reset the card. Report the error to TAC."
REQUIRED INFO "Take core dump. Collect event and error logs."

SSI-4-ME_SEMCREATEFAI

SEVERITY: Error
FORMAT: "SSI ME Sem creation failed for Active Op Table. Errno=0x%x."
FLAG: Write to Bram
THROTTLING One Tick
EXPLANATION: "Creation of semaphore for SSI ME Active Operation Table failed unexpectedly. SSI Mutual Exclusion functionality 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. 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

SSI-7-ME_SEMTAKEFAIL

SEVERITY: Information
FORMAT: "Take of semaphore %p for Active Op Table failed. Errno=0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The Take of the semaphore for the SSI ME Active Op Table failed It is likely that another task is holding the sem as there is no wait allowed. This isan expected occurrence. However, if the problem persists it could be due to memory corruption.".
RECOMMENDED ACTION: "If this problem persists, reset the card."
REQUIRED INFO "In the case of repeated occurrences Take core dump. Collect event and error logs."

SSI-5-ME_SEMGIVEFAIL

SEVERITY: Warning
FORMAT: "Give of semaphore %p for Active Operation Table failed. Errno=0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The Take of the semaphore for the SSI ME Active Op Table failed unexpectedly. This could be due to memory corruption. This may affect the SSI Mutual Exclusion functionality."
RECOMMENDED ACTION: "If this problem persists, reset the card."

REQUIRED INFO "Take core dump. Collect event and eSSI-5-ME_OPTBLFULL

SEVERITY: Warning
FORMAT: "The SSI ME Active Op Table is full. There are %d current entries."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The SSI ME Active Op Table is full. There are no entries available at this time. Entries may become available when other operations have completed. If this problem persists, a consistency check and possibly a table cleanup is required."
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

SSI-4-ME_DUPLENTRY

SEVERITY: Error
FORMAT: "A lock on resource %s by Task 0x%x for operation %d already exists."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The calling task has tried to lock a resource which it has already locked for the same operation. This type of duplicate lock is not allowed."
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

SSI-4-ME_INVALIDOPKEY

SEVERITY: Error
FORMAT: "The Operation Key 0x%x passed is invalid."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "API Software Error. The value for the SSI ME Operation Key passed in as an argument to the named function was invalid."
RECOMMENDED ACTION: "Look for the events logged by the module/function calling the specified API function and take the actions recommended for those events."
REQUIRED INFO "Collect the event and error logs."

SSI-4-ME_TASKNOTOWNER

SEVERITY: Error
FORMAT: "Task (0x%x) is not the owner of key 0x%x. Owner=(0x%0x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A process that is not the owner of a lock on an SSI ME resource is attempting to unlock that resource. This indicates a software 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

SSI-5-ME_LOCKFAIL

SEVERITY: Warning
FORMAT: "An attempt by task 0x%x to lock resource %s for op %d has failed."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An attempt to lock a resource by the specified task has failed. This may be innocuous, e.g. the resource may already be locked by another task. Consult the event log for events leading up to this occurrence."
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 "Take core dump. Collect event and error logs."

SSI-4-ME_UNLOCKFAIL

SEVERITY: Error
FORMAT: "An attempt to unlock a resource using key 0x%x has failed."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An attempt to unlock a resource by the specified task has failed. Consult the event log for events leading up to this occurrence."
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 "Take core dump. Collect event and error logs."

SSI-4-ME_INDEXFAIL

SEVERITY: Error
FORMAT: "Incorrect value %d was given as index into the Active Op Table."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An incorrect index value was returned when trying to locate a free entry in the Active Op Table. This is a software 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 "Take core dump. Collect event and error logs."

SSI-5-ME_INTPARMINVAL

SEVERITY: Warning
FORMAT: "Parm %s value '0x%x' is invalid to %s."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Internal Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."
RECOMMENDED ACTION: "Look for the events logged by the module/function calling the specified API function and take the actions recommended for those events."
REQUIRED INFO "Collect the event and error logs."

SSI-5-ME_TASKSAFEFAIL

SEVERITY: Warning
FORMAT: "A call to ssiTaskSafe for Task 0x%x failed."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A call to ssiTaskSafe failed while locking a resource. This Task is not safe from deletion, and is holding locks on resources."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

SSI-4-ME_TASKUNSAFEFA

SEVERITY: Error
FORMAT: "A call to ssiTaskUnsafe for Task 0x%x failed."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A call to ssiTaskUnsafe failed while attempting to unlock a resource. This task cannot currently be deleted."
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

SSI-7-CHNK_UNIT_TEST

SEVERITY: Information
FORMAT: "unit-test info %s"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "Generic event to log information in unit-tests. Unit tests may log errors (when testing the lib with invalid parameters and corrupted chunks for example). Before attempting an operation that we expect to fail, unit test log this information event so that when inspecting the logs, we know the next chunk error(s) were expected or we can also spot missing errors that should normally have been logged during unit tests."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-7-CHNK_GROW_SHRIN

SEVERITY: Information
FORMAT: "%s chunk pool name=[%s] nbSubPools=[%d] nbChunk=[%d]"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Information message for important events that might happen to chunk pools such as growth or shrink (not an error). These events should not happen often because there is a hysteresis effect so that a chunk does not shrink just after growing (and the other way around)."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-7-CHNK_FREE_LEAK

SEVERITY: Information
FORMAT: "chunk leak in pool [%p/%s] leakThresholdInSec=[%d] nbLeaks=[%d] nbLeaksFreed=[%d]"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Chunk leak were detected and freed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-CHNK_LOW_PRIO

SEVERITY: Warning
FORMAT: "name=[%s] callerPc=0x%x nbFreeChunks=%d maxNbChunks=%d nbChunks=%d lowThreshold=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Allocation failed because nbFreeChunks is below threshold and chunk allocation had a low priority. It can be the result of a chunk leak the pool."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-5-CHNK_STATE_LOW

SEVERITY: Warning
FORMAT: "Chunk pool state low index=%d name=[%s] callerPc=0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Number of free chunks in a pool becomes low. the chunk pool is almost full. It can be the result of a chunk leak in the pool. CTC is informed of state transition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-7-CHNK_STATE_OK

SEVERITY: Information
FORMAT: "chunk pool state OK index=%d name=[%s] callerPc=0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Number of free chunks in a pool becomes OK (above threshold). CTC is informed of the state transition."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SSI-4-CHNK_UNIQ_NAME

SEVERITY: Error
FORMAT: "non-unique chunk pool name=[%s]"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "At least 2 chunk pools have been created with same names. Chunk pool names are supposed to be unique. As a result, chunk pool creations failed. This is a chunk API usage error."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "Collect the event and error logs."

SSI-4-CHNK_ALRDY_GROW

SEVERITY: Error
FORMAT: "chunk pool name=[%s] growth policy already defined"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Growing policy of a chunk pool can only be defined once. This is an API usage error."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "Collect the event and error logs."

SSI-4-CHNK_POOL_INV

SEVERITY: Error
FORMAT: "invalid invariant, poolIdx=[%d] [%s]=[%d]"
FLAG: No Flag
THROTTLING Thirty Seconds
EXPLANATION: "An invalid assertion or invariant was found at a pool level while performing sanity check of a chunk pool. It is an internal error in the chunk lib or memory corruption."
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 the event and error logs."

SSI-4-CHNK_SUBPOOL_IN

SEVERITY: Error
FORMAT: "invalid chunk sub-pool invariant, poolIdx=[%d] subPoolIdx=[%d] [%s]=[%d]"
FLAG: No Flag
THROTTLING Thirty Seconds
EXPLANATION: "An invalid assertion or invariant was found at a sub-pool level while performing sanity check in a chunk sub-pool. It is an internal error in the chunk lib or memory corruption."
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 the event and error logs."

SSI-4-CHNK_INV

SEVERITY: Error
FORMAT: "line=%d chunk=%p pool=%d flag=0x%x rfCnt=%d nxtFree=0x%x own=%p call=0x%x"
FLAG: No Flag
THROTTLING Thirty Seconds
EXPLANATION: "An invalid assertion or invariant was found at a chunk level while performing sanity check in a chunk pool. It can either be a chunk lib internal error or a chunk memory overflow by chunk user."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. 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 the event and error logs."

SSI-4-CHNK_TOO_MNY_PO

SEVERITY: Error
FORMAT: "max nb of chunk pool reached name=[%s]"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "no more chunk pool available, too many chunk pools have been created."
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 the event and error logs."

SSI-4-CHNK_XNOT_USED

SEVERITY: Error
FORMAT: "pool=[%s] ptr=%p flags=0x%x cnt=%d own=%p(%s) caller=0x%x/0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A task tried to free an already freed chunk."
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 the event and error logs."

SSI-4-CHNK_NOT_USED

SEVERITY: Error
FORMAT: "pool=[%s] p=%p flags=0x%x caller=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A task tried to free an already freed chunk."
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 the event and error logs."

SSI-4-CHNK_POOL_NOT_F

SEVERITY: Error
FORMAT: "pool=[%s] nbFreeChunks=[%d] nbChunks=[%d]"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Trying to delete a chunk pool when there are still chunks that have not been freed yet. As a result, the chunk pool will not be freed and a significant amount of memory might be leaked."
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 the event and error logs."

SSI-4-CHNK_INV_PARAM

SEVERITY: Error
FORMAT: "invalid input parameter [%s]=[0x%x] [0x%x]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A chunk API function received an invalid or out of range input parameter. It is a chunk API usage error."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "Collect the event and error logs."

SSI-4-CHNK_INT_ERROR1

SEVERITY: Error
FORMAT: "chunk internal error [%s] [0x%x]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "This is a generic error for chunk lib internal error. This error may happen as a result of a software bug in SSI chunk implementation or memory corruption"
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 the event and error logs."

SSI-4-CHNK_INT_ERROR2

SEVERITY: Error
FORMAT: "chunk internal error [%s] [0x%x] [0x%x]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "This is a generic error for chunk lib internal error. This error may happen as a result of a software bug in SSI chunk implementation or memory corruption"
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

SSI-4-CHNK_INT_ERROR3

SEVERITY: Error
FORMAT: "chunk internal error [%s] [0x%x] [0x%x] [0x%x]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "This is a generic error for chunk lib internal error. This error may happen as a result of a software bug in SSI chunk implementation or memory corruption"
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 the event and error logs."

SSI-4-CHNK_INT_ERROR4

SEVERITY: Error
FORMAT: "chunk internal error [%s] [0x%x] [0x%x] [0x%x] [0x%x]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "This is a generic error for chunk lib internal error. This error may happen as a result of a software bug in SSI chunk implementation or memory corruption"
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 the event and error logs."

SSI-4-CHNK_REF_COUNT

SEVERITY: Error
FORMAT: "chunk pool=[%s] invalid refCount=[0x%x]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Ref count has an illegal value. A chunk has been duplicated too many times."
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 the event and error logs."

SSI-4-CHNK_INV_DATA_P

SEVERITY: Error
FORMAT: "invalid chunk data ptr [%s]=[%p]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Chunk API received an invalid chunk ptr as input parameter. Invalid usage of the SSI chunk API. The chunk ptr received by chunk API did not match any existing chunk pointer."
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 the event and error logs."

SSI-4-CHNK_WRONG_TID

SEVERITY: Error
FORMAT: "wrong task op=[%s] tid=[%p(%s)/%p(%s)] ptr=[%p] rfc=[%d] poolIdx=[%d] name=[%s]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A chunk level operation (described by op value in formatted message) has been attempted by a task which does not owns the chunk, operation was denied."
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 the event and error logs."

SSI-4-CHNK_PERM_TID

SEVERITY: Error
FORMAT: "wrong task id=[%p] exp=[%p] name=[%s]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A chunk pool level operation has been attempted by a task which does not own the pool (wrong task id)"
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 the event and error logs."

SSI-4-CHNK_PERM_CTC

SEVERITY: Error
FORMAT: "wrong ctcAppid=[%p] exp=[%p] name=[%s]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A chunk pool level operation has been attempted by a task which does not own the pool (wrong ctc appid)"
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 the event and error logs."

SSI-4-CHNK_XCORR

SEVERITY: Error
FORMAT: "[%s] %p %x %x/%x %x/%x %x/%x %x/%x/%x %s/%s/%s %x/%x/%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A task corrupted a shared data chunk (probably as a result of a write overflow in a data chunk). Magic number and/or indexes in data header are corrupted. Consequences are unpredictable. Chunk lib should be robust enough to continue working correctly but user of corrupted chunk may have troubles."
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 "Take core dump. Collect event and error logs."

SSI-4-CHNK_CORR

SEVERITY: Error
FORMAT: "[%s] %p %x %x/%x %x/%x %x/%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A non-shared data chunk is corrupted (probably as a result of write overflow in a data chunk). Magic number and/or indexes in data header are corrupted. Consequences are unpredictable. Chunk lib should be robust enough to continue to work correctly but user of corrupted chunk may have troubles."
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 "Take core dump. Collect event and error logs."

SSI-4-CHNK_XCTOR

SEVERITY: Error
FORMAT: "chunk corrupted next one poolIdx=%d p=%p task=%s caller=0x%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Chunk corrupted the next one"
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 "Take core dump. Collect event and error logs."

SSI-4-CHNK_CTOR

SEVERITY: Error
FORMAT: "chunk corrupted next one poolIdx=%d p=%p"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Chunk corrupted the next one"
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 "Take core dump. Collect event and error logs."

SSI-4-CHNK_ISR_POOL

SEVERITY: Error
FORMAT: "illegal operation on ISR callable chunk pool idx [%d]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "An operation has been attempted on a ISR callable chunk and is not allowed for ISR callable chunk."
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 the event and error logs."

SSI-4-CHNK_SHARED_POO

SEVERITY: Error
FORMAT: "illegal operation on shared chunk pool idx [%d]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A chunk function has been invoked on a shared pool which only applies for unshared chunk pools (or the other way around). This is probably a chunk API usage error"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "Collect the event and error logs."

SSI-4-CHNK_EXT_HDR

SEVERITY: Error
FORMAT: "operation on chunk pool [%s] requires extended header"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Chunk pool should have been created with SSI_CHUNK_POOL_UFLAG_EXT_HDR option in order for this operation to succeed"
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 the event and error logs."

SSI-4-CHNK_UNUSED_POO

SEVERITY: Error
FORMAT: "illegal operation on unused pool index=[%d]"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "A chunk function has been invoked on an unused chunk pool. A chunk user may have given a wrong chunk pool id or is using a chunk pool that has been deleted."
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 the event and error logs."

SSI-5-CHNK_FULL_POOL

SEVERITY: Warning
FORMAT: "chunk pool full, index=%d name=[%s] callerPc=0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A chunk pool is full and cannot grow. This can be the result of a chunk leak."