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

SHMA-7-MSG_NOT_SUPPORT

Table Of Contents

SHMA-7-MSG_NOT_SUPPORT

DDTS "csrsmcnf"

SMCS-4-RSRC_ERROR

SMCS-4-IPCSNDRCV_ERROR

SMCS-4-STANDBY_UPDATE_

SMCS-4-API_TIMEOUT_ERR

SMCS-4-TASK_INTERNAL_E

SMCS-4-AC_DBUPDATE_ERR

SMCS-4-AC_SHM_ERROR

SMCS-4-PXMCM_FAILURE

SMCS-4-DISK_IPC_FAIL

SMCS-4-DISK_CLNUP_FAIL

SMCS-4-DISK_STBY_STATE

SMCS-4-DISK_INVALID_SL

SMCS-4-DISK_INVALID_CD

SMCS-4-DISK_STBY_SIG_F

SMCS-4-DISK_ERROR

SMCS-4-RMM_CLRSMCNF_ER

SMCS-4-FATAL_ERR_PNNI

SMCS-7-INFO_PNNI

SMCS-6-NOTICE_PNNI

SMCS-5-WARNING_PNNI

SMCS-4-ERROR_PNNI

SMCS-7-CONGEST_PNNI

SMCS-7-NULL_PTR_PNNI

SMCS-7-MALLOC_FAIL_PNN

SMCS-7-TIMEOUT_PNNI

SMCS-7-ABORT_FAIL_PNNI

SMCS-7-INTF_PNNI

SMCS-7-TREE_NOTEMPTY_P

SMCS-7-PEP_PNNI

SMCS-7-DISK_FAIL_PNNI

SMCS-7-START_END_PNNI

SMCS-7-BUFFER_UPDT_PNN

SMCS-7-REDO_UPDT_PNNI

DDTS "control-point"

MIBS-7-INFO

MIBS-7-INFO_RETRY

EMAN-5-PARMINVALID

EMAN-5-INVALID_PTR

EMAN-5-INVALID_PTR2

DDTS "control-point"

RTM-5-INVALIDINPUT

RTM-5-PARMINVALID

RTM-5-PARMINVLENGTH

RTM-5-FUNCFAIL_STKDUM

RTM-5-FUNCFAIL

RTM-5-PARMOUTOFRANGE

RTM-5-MALLOCFAILED

RTM-5-OPEN_TRANS_FAIL

RTM-5-BIND_TRANS_FAIL

RTM-5-CNTP_MSGSEND_FA

RTM-5-CNTP_MSGRECV_FA

RTM-5-DB_INIT_FAIL

RTM-5-INVALID_SRM_SLO

RTM-5-UNKNOWN_CARD_TY

RTM-5-INVALID_VARBIND

RTM-5-CNTP_SEMCREATE_

RTM-5-CNTP_SEMTAKE_ER

RTM-5-CNTP_SEMGIVE_ER

RTM-5-CNTP_MSGBUFTAKE

RTM-7-TRAPS_NOT_ALLOW

RTM-6-TRAPLOG_WRAP

RTM-6-RPM_PORT_CLOSED

RTM-5-RPM_OPEN_PORT_F

RTM-5-OPEN_PORT_FAILE

RTM-5-PROCESS_DEQUEUE

RTM-5-CREATE_WATCHED_

RTM-5-CREATE_NAMED_PO

RTM-5-IPC_GET_PAK_MSG

RTM-5-IPC_SEND_MSG_FA

RTM-5-MSG_TOO_SMALL

RTM-5-PXM_SOI_INIT_FA

RTM-5-RAM_DB_INIT_FAI

RTM-5-RAMTBL_REGISTRY

RTM-5-RAM_TBL_STDBY_U

RTM-5-DB_UPDATE_BAD_A

RTM-5-DB_UPDATE_NUM_E

DDTS "control-point"

MIBS-5-SEMCREATE_FAILE

MIBS-5-SEMTAKE_FAILED

MIBS-5-SEMGIVE_FAILED

MIBS-5-SEMTAKE_TASK

MIBS-5-SEMTAKE_RECOVER

DDTS "snmp"

SRAT-4-TASKDELAYERROR

SRAT-4-CRD_STATE_EXPIR

SRAT-4-GENERIC_ERROR

DDTS "snmp-sa"

SUBA-4-FAILED_RESOLVE_

SUBA-4-FAILED_CREATE_E

SUBA-4-FAILED_BIND_EPI

SUBA-4-FAILED_MALLOC

SUBA-4-FAILED_IPCMSG_A

SUBA-4-FAILED_IPCSEND

SUBA-4-IPCDATAPTR_INVA

SUBA-7-SAREGISTER

SUBA-7-SADEREGISTER

SUBA-7-SASTATECHANGE

SUBA-7-SAREQUEST_FAILE

SUBA-5-INVALID_TYPE

DDTS "sntp"

SNTP-4-pSntpInitErr

SNTP-7-INFO

SNTP-7-INFO_D

SNTP-7-INFO_S

SNTP-7-INFO_IP

SNTP-7-INFO_IPD

SNTP-7-INFO_IPD_RTD

SNTP-7-INFO_IPD_IPD

SNTP-5-WARN

SNTP-5-WARN_D

SNTP-5-WARN_S

SNTP-5-WARN_IP

SNTP-5-WARN_IPD

SNTP-5-WARN_IPD_IPD

SNTP-5-ERROR

SNTP-5-ERROR_D

SNTP-5-ERROR_S

SNTP-5-ERROR_IP

SNTP-5-ERROR_IPD

SNTP-5-ERROR_IPD_IPD

SNTP-5-ERROR_UNKNOWN_M

SNTP-7-SNTP_CLIENT_RCV

SNTP-7-SNTP_SERVER_RCV

DDTS "spvc"

SPFM-3-DRVINIT

SPFM-5-SPFM_WARNING

SPFM-7-SPFM_INFORMATIV

DDTS "pxm-connmgm"

SPI-4-SDRV_PATH_ERR

SPI-4-SDRV_CD_ERR

SPI-4-SDRV_VI_ERR

SPI-4-SDRV_QB_ERR

SPI-4-SDRV_ERR

SPI-4-SDRV_CONNREF_ER

SPI-4-SDRV_CONNREF_OU

SPI-5-SDRV_PEER_TX_NO

SPI-4-SDRV_CONNTYPE_O

SPI-4-SDRV_POOL_FULL

SPI-4-SDRV_POOL_EMPTY

SPI-4-SDRV_RSRC_OUTOF

SPI-4-SDRV_RSRC_DUP

SPI-4-SDRV_CONN_CMT

SPI-4-SDRV_CONN_MAP_F

SPI-4-SDRV_PATHADD_FA

SPI-4-SDRV_CONN_NOTCM

SPI-4-SDRV_PATHCFG_FA

SPI-4-SDRV_POOL_CORRU

SPI-4-SDRV_SARLCN_ERR

SPI-4-SDRV_PATHTYPE_I

SPI-4-SDRV_POOLGET_ER

SPI-4-VISWAPPING

SPI-4-SDRV_MEMALLOC_E

SPI-5-SDRV_OUTOF_CONN

SPI-5-SDRV_OUTOF_ROOT

SPI-5-SDRV_OUTOF_LEAF

SPI-5-SDRV_INVALID_RO

DDTS "unknown"

SPM-7-SHELFDB_INIT

SPM-7-SPM_SMDB_INIT

SPM-4-SPM_EPTDB_BAD

SPM-7-RM_RAMDB_INIT

SPM-7-SPM_TIMER_ERROR

SPM-7-SPM_MEM_ERROR

SPM-7-SPM_MSG_ERROR

SPM-7-SPM_ERR_GEN

SPM-4-RM_API_ERROR

SPM-4-RM_NULL_PTR

DDTS "unknown"

SPM-7-SPM_SHELFDB_INI

SPM-7-SPM_SMDB_INIT

SPM-2-SPM_EPTDB_BAD

SPM-7-SPM_RM_RAMDB_IN

SPM-7-SPM_TIMER_ERROR

SPM-7-SPM_MEM_ERROR

SPM-7-SPM_MSG_ERROR

SPM-7-SPM_TASK

DDTS "spvc"

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-4-SWERROR

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVM-5-WARNING

SPVM-7-INFO

SPVM-7-DINFO

SPVM-4-ERROR

SPVM-7-COMMAND

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-5-WARNING

SPVC-7-INFO

SPVC-7-DINFO

SPVC-4-ERROR

SPVC-4-ERROR

SPVC-4-ERROR

DDTS "srm"

SRM-7-SRM_SYNCRAM

SRM-4-SRM_SYNCRAM_UPD

SRM-4-DBTBLINIT_ERR

SRM-4-SRMCT_DBREG_ERR

SRM-4-DBTBLIDINVLD

SRM-4-HS_INVLD_UPDACT

SRM-4-HS_INVLD_UPDATE

SRM-4-SRMCT_INIT_ERR

SRM-7-SRMCT_CD_INS

SRM-7-SRMCT_CD_REM

SRM-7-SRMCT_BC_INS

SRM-7-BC_MISSING

SRM-7-UNKNOWN_STATE

SRM-7-UNKNOWN_SRM

SRM-7-PIO_INIT_FAIL

SRM-7-CARD_LOOSE

SRM-7-XIL_IMG_ID

SRM-7-XIL_IMG_ERR

SRM-7-XIL_DNLD_FAIL

SRM-7-FPGA_LOAD_FAIL

SRM-7-NVRAM_CHECKSUM_

SRM-7-SRMCT_FAIL_MSG

SRM-7-INVALID_MSG

SRM-7-CLR_SRM_CNF

SRM-7-CLR_SRM_CNF_ERR

SRM-4-SRM_HW_UNSUPPOR

SRM-7-LEGACY_ERR_RPT

SRM-7-SRME_ERR_RPT

SRM-7-IPC_ERR

SRM-7-SRME_UNKNOWN_CL

SRM-4-ONLINE_DIAG_ERR

SRM-4-OFFLINE_DIAG_ER

SRM-7-RAM_SYNC_IOV_FA

DDTS "atmsig"

SSCO-4-SSCOP_NOMEM_WAR

SSCO-4-SSCOP_NOBUF_WAR

SSCO-4-SSCOP_NOMEM_MAJ

SSCO-4-SSCOP_CBPOOL_IN

SSCO-4-SSCOP_SRCHHELPE

SSCO-4-SSCOP_EP_CREAT_

SSCO-2-SSCOP_STG1_INIT

SSCO-3-SSCOP_INIT_FAIL

SSCO-4-SSCOP_CBPOOL_HN

SSCO-4-SSCOP_TMRLIB_ER

SSCO-4-SSCOP_NULLPTR

SSCO-7-SSCOP_NULLCTLBL

SSCO-4-SSCOP_NULLIDB

SSCO-6-SSCOP_VCUPMSG

SSCO-6-SSCOP_VCDOWNMSG

SSCO-4-SSCOP_VCBINDFAI

SSCO-4-SSCOP_CTLBLK_IN

SSCO-4-SSCOP_CTLBLK_DE

SSCO-4-SSCOP_WAVL_DEL_

SSCO-4-SSCOP_CLR_EPID

SSCO-6-SSCOP_INTF_ADD

SSCO-4-SSCOP_INTF_TXQ_

SSCO-6-SSCOP_INTF_EXIS

SSCO-6-SSCOP_INTF_NOT_

SSCO-6-SSCOP_INTF_DEL

SSCO-4-SSCOP_OPENFAIL

SSCO-4-SSCOP_CLOSEFAIL

SSCO-5-SSCOP_VCUNBINDF

SSCO-4-SSCOP_FREE_LIST

SSCO-6-SSCOP_FREE_LIST

SSCO-4-SSCOP_CNF_FAIL

SSCO-4-SSCOP_UNKNOWN_S

SSCO-4-SSCOP_UNKNOWN_E

SSCO-4-SSCOP_IPC_SEND_

SSCO-4-SSCOP_INV_PAK

SSCO-4-SSCOP_INV_SSCOP

SSCO-6-SSCOP_RESOLV_EP

SSCO-4-SSCOP_INIT_CB

SSCO-6-SSCOP_TMR_EXP

SSCO-4-SSCOP_TMR_EXP_E

SSCO-4-UNEXPECTEDTIMER

SSCO-6-SSCOP_LINK_EST

SSCO-6-SSCOP_LINK_REL

SSCO-6-SSCOP_LINK_RST

SSCO-4-SSCOP_SEQ_ERR

SSCO-5-SSCOP_PEER_VER_

SSCO-5-SSCOP_PEER_VER_

SSCO-6-SSCOP_INIT

SSCO-4-SSCOP_PROV_REBU

SSCO-6-SSCOP_TASK_ST_C

SSCO-6-SSCOP_TASK_WRON

SSCO-4-SSCOP_TMR_FATAL

SSCO-4-SSCOP_TMR_STOP_

SSCO-4-SSCOP_CONGAPI_E

SSCO-4-SSCOP_HIRESND_R

SSCO-6-SSCOP_DBGLOG

SSCO-6-SSCOP_DUP_VCUP_

SSCO-6-SSCOP_DUP_VCUP_

SSCO-6-SSCOP_VC_BIND_M

SSCO-6-SSCOP_VC_UNBIND

SSCO-6-SSCOP_INVALID_V

DDTS "ssi"

DTAP-4-INVALID_CONID

DTAP-5-TOOMANYCONS

DTAP-5-INVALID_CONNAME

DTAP-5-INVALID_PARM

DTAP-5-INVALID_DATALEN

DTAP-4-INVALID_BUFFER

DTAP-5-INVALID_RECVAPI

DTAP-5-INVALID_REREG

DTAP-5-INVALID_MSGSIZE

DTAP-5-INVALID_EPID

DTAP-5-FAILED_ALLOC

DTAP-5-FAILED_PROTOEVT

DTAP-5-INVALID_FUNC

DDTS "ssi"

FAS-5-SEMTAKE

FAS-2-SEMGIVE

FAS-4-FDINVALID

FAS-4-MAXSZTOOSMALL

FAS-5-NOTREADY

FAS-3-FDFULL

FAS-3-REQUNKNOWN

FAS-5-DTINUSE

FAS-4-PARAMINVALID

FAS-5-TIDINVALID

FAS-5-WARNING

FAS-5-WRVER

FAS-1-CTCDBLD

FAS-1-CTCDBSYNC

FAS-1-CTCGOREADY

FAS-5-IPWAIT

FAS-1-SEMCREATE

FAS-1-EVTHDLR

FAS-2-DRVINIT

FAS-2-DEVADD

FAS-5-READOP

FAS-5-LOGPART

FAS-5-DEVNM

FAS-5-BDINPUT

FAS-5-BDSTBYSLOT

FAS-5-DIOFILELOCKTAKE

FAS-5-DIOOPEN

FAS-5-DIOCOPY

FAS-5-IPCMSGALLOC

FAS-5-DATAXFERMSGALLO

FAS-7-INFO

DDTS "ssi"

FIPC-1-FATAL_ERROR

FIPC-2-MAJOR_ERROR

FIPC-4-ERROR_STKYES

FIPC-4-ERROR_STKNO

FIPC-5-WARNING

FIPC-7-INFO

FIPC-4-COMEPPARAMINVAL

FIPC-4-COMEPSEMTAKE

FIPC-5-ISRNOTCALLABLE

FIPC-5-MCASTPSLOTINVAL

FIPC-5-MCASTPORTINVAL

FIPC-4-COMEPMALLOCERR

FIPC-4-NUMCOMEPINVALID

FIPC-4-COMEPMEMAREAERR

FIPC-5-COMEPALLOCFAIL

FIPC-5-COMEPFREEFAIL

FIPC-5-COMEPIDINVALID

FIPC-5-COMEPDELETED

FIPC-5-COMEPOWNERINVAL

FIPC-5-COMEPTYPEINVAL

FIPC-4-COMEPSEMINVALID

FIPC-4-COMEPNAMEINVAL

FIPC-5-COMEPNAMESCOINV

FIPC-4-COMEPRPLYEPDINV

FIPC-5-EPHNDLRFAIL

FIPC-5-EPHNDLRATTACHED

FIPC-5-EPWAITEXTINVPRM

FIPC-5-SYNCCTXTINUSE

FIPC-4-SYNCCTXTCLNERR

FIPC-5-SYNCINVALIDRPLY

FIPC-5-SYNCNOTSYNCRPLY

FIPC-4-MSGQDELETEFAIL

FIPC-4-MSGQCREATEFAIL

FIPC-4-MSGQDEAD

FIPC-4-HIGHMSGQDEAD

FIPC-4-LOWMSGQDEAD

FIPC-4-MSGQEVENT

FIPC-4-RETXQSIGLCKFAIL

FIPC-4-RETXQSGUNLKFAIL

FIPC-5-RETXQMQCHAINERR

FIPC-5-RETXQTIMERSET

FIPC-5-RETXQTIMRCANCEL

FIPC-4-MBLKMPOOLCRTERR


SHMA-7-MSG_NOT_SUPPORT

SEVERITY : Information
FORMAT : "Msg Type %d(%s) is not supported by Active PXM"
FLAG : Write Bram
THROTTLING : No Throttling
EXPLANATION : "The specified message type is not supported by the Active PXM and so will be NACKed by the Active PXM. This should happen only after loadrev on the PXM pair. When the Active PXM is running a lower revision."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO : No Required Info

DDTS "csrsmcnf"

SMCS-4-RSRC_ERROR

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Insufficient System Resources Available"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore due to insufficient available system resources like memory, ipc messages"
RECOMMENDED ACTION: "Check system resources & Try again"
REQUIRED INFO "Collect dsplog, dsperr information"

SMCS-4-IPCSNDRCV_ERROR

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s IPC Message Send Problem"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore due to IPC messaging Problem"
RECOMMENDED ACTION: "Check system resources & Try again"
REQUIRED INFO "Collect dsplog, dsperr information"

SMCS-4-STANDBY_UPDATE_

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s standby PXM update Failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore due to failure of PXM standby update for the logged task"
RECOMMENDED ACTION: "Check Task & Standby PXM health and try Again"
REQUIRED INFO "Collect dsplog, dsperr information"

SMCS-4-API_TIMEOUT_ERR

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Timed Out"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore due to failure of the task to the operation within the specified timeout period"
RECOMMENDED ACTION: "Check Task health and PXM CPU usage and Try Again"
REQUIRED INFO "Collect dsplog, dsperr information"

SMCS-4-TASK_INTERNAL_E

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Task Error"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore due to internal error in the logged task"
RECOMMENDED ACTION: "Check for task related event logs and take suitable action"
REQUIRED INFO "Collect dsplog, dsperr information"

SMCS-4-AC_DBUPDATE_ERR

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Disk Update Failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as Disk Modification Request Failed"
RECOMMENDED ACTION: "Indicates an internal error, It needs to be analyzed by TAC and possibly by development team."
REQUIRED INFO "Collect dsplog, dsperr, dspdbinfo <slot> 3 information"

SMCS-4-AC_SHM_ERROR

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Request To SHM Failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as Request to ShelfMgr Task Failed"
RECOMMENDED ACTION: "Indicates an internal error, It needs to be analyzed by TAC and possibly by development team."
REQUIRED INFO "Collect dsplog, dsperr, dspcd <slot> information"

SMCS-4-PXMCM_FAILURE

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Failed to delete Port/Partition properly"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as PXMCM Failed"
RECOMMENDED ACTION: "Indicates an internal error detected by the PXMCM It needs to be analyzed by TAC and possibly by the development team."
REQUIRED INFO "Please capture the following information from the and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot having the problem>
4) dsperr for the above slots.
5) Save the core file if required"

SMCS-4-DISK_IPC_FAIL

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s IPC Related Error"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as some IPC related function called by Disk application failed. "
RECOMMENDED ACTION: "Check the error log for the specifc IPC related error logged by the dbSvr task. Also look for events that have been logged by the IPC or other tasks to indicate the nature of the IPC problem"
REQUIRED INFO "Please capture the following information and call your TAC support
1) dspver
2) dsplog -sl <slot having the problem> "

SMCS-4-DISK_CLNUP_FAIL

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Db cleanup for
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as the cleanup for the slot failed. Most probably a call to dbio_cleanup_slot_info() function returned ERROR"
RECOMMENDED ACTION: "Check event logs to find the event logged by disk regarding a failure to clean the slot info. "
REQUIRED INFO "Please capture the following information and call your TAC support
1) dspver
2) dsplog "

SMCS-4-DISK_STBY_STATE

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Could not get standby card state."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task could not get the state of the stdby slot. Most probably a call to dbio_standby_card_state_get() function returned ERROR"
RECOMMENDED ACTION: "Check event logs to find the event logged by disk regarding a failure to get the standby card state. "
REQUIRED INFO "Please capture the following information and call your TAC support
1) dspver
2) dsplog -sl <standby slot > "

SMCS-4-DISK_INVALID_SL

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Was passed invalid slot for clearing "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task was passed a slot that is not valid for clrsmcnf"
RECOMMENDED ACTION: " Try clrsmcnf on valid slot"
REQUIRED INFO "Please capture the following information and call your TAC support
1) dspcd <slot_number>
2) dspcds"

SMCS-4-DISK_INVALID_CD

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s clrsmcnf was invoked on standby card."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task detected the command being executed on a card that is not the active card "
RECOMMENDED ACTION: "Try clrsmcnf on valid card role"
REQUIRED INFO "Please capture the following information and call your TAC support
1) dspcd <active_pxm_slot>
2) dspcds"

SMCS-4-DISK_STBY_SIG_F

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s Could not create a signature file"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task could not create signature file"
RECOMMENDED ACTION: "Try clrsmcnf again"
REQUIRED INFO "Please capture the following information and call your TAC support
1) dspver
2) dsplog"

SMCS-4-DISK_ERROR

SEVERITY: Error
FORMAT: "SMCSR Operation Failed Task %s : A general error occurred."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SMCSR Failed to do clear/save/restore as the dbSvr task failed to carry out required function"
RECOMMENDED ACTION: "Try clrsmcnf again"
REQUIRED INFO "Please capture the following information and call your TAC support
1) dspver
2) dsplog
3) dsperrs"

SMCS-4-RMM_CLRSMCNF_ER

SEVERITY: Error
FORMAT: "Clrsmcnf failed. Task %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error while open/modify an auto_config file."
RECOMMENDED ACTION: "Check system resources & Try again"
REQUIRED INFO "Please capture the following information
1) dspver
2) dsplog
3) dsperrs"

SMCS-4-FATAL_ERR_PNNI

SEVERITY: Error
FORMAT: "Clrsmcnf failed. %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Pnni module failed Clrsmcnf for un-recoverable error."
RECOMMENDED ACTION: "Check for task related event logs"
REQUIRED INFO "Collect dsplog, dsperr information"

SMCS-7-INFO_PNNI

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

SMCS-6-NOTICE_PNNI

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

SMCS-5-WARNING_PNNI

SEVERITY: Warning
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "something during CSRSmcnf that may cause potential problem to the system"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO "dsplog -mod CSR; dspconinfo; dsppnports"

SMCS-4-ERROR_PNNI

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "internal software error"
RECOMMENDED ACTION: "talk to developer engineer to identify problem"
REQUIRED INFO "capture logs, especially dsplog -mod CSR; dspconinfo; dsppnports; Go to standby, do the same display"

SMCS-7-CONGEST_PNNI

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

SMCS-7-NULL_PTR_PNNI

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

SMCS-7-MALLOC_FAIL_PNN

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

SMCS-7-TIMEOUT_PNNI

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

SMCS-7-ABORT_FAIL_PNNI

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

SMCS-7-INTF_PNNI

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

SMCS-7-TREE_NOTEMPTY_P

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

SMCS-7-PEP_PNNI

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

SMCS-7-DISK_FAIL_PNNI

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

SMCS-7-START_END_PNNI

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

SMCS-7-BUFFER_UPDT_PNN

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

SMCS-7-REDO_UPDT_PNNI

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

DDTS "control-point"

MIBS-7-INFO

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

MIBS-7-INFO_RETRY

SEVERITY : Information
FORMAT : "%d: %s %d"
FLAG : No Flag
THROTTLING : One Tick
EXPLANATION : "Subagent retry to register with master agent"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO : No Required Info

EMAN-5-PARMINVALID

SEVERITY: Warning
FORMAT: "%d Parm %s value '0x%x'."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

EMAN-5-INVALID_PTR

SEVERITY : Warning
FORMAT : "%d: %s %p"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Pointer is not safe to dereference."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO : No Required Info

EMAN-5-INVALID_PTR2

SEVERITY : Warning
FORMAT : "%d: %s %p %s %p %d"
FLAG : Stack Trace
THROTTLING : One Tick
EXPLANATION : "Pointer is not safe to dereference."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO : No Required Info

DDTS "control-point"

RTM-5-INVALIDINPUT

SEVERITY: Warning
FORMAT: "One of the inputs to the function %s() was invalid."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "API Software Error. The parameter value for one of the parameters passed in as an argument to the named function was invalid."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-PARMINVALID

SEVERITY: Warning
FORMAT: "Parm %s value '0x%x' is invalid to %s."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-PARMINVLENGTH

SEVERITY: Warning
FORMAT: "Parm %s invalid length of %d to %s. Max=%d Value='%s'"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "API Software Error. The named paramater passed in as an argument to the named function either had a length of zero or exceeded the maximum value specified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-FUNCFAIL_STKDUM

SEVERITY: Warning
FORMAT: "%s() RTM subsystem call to %s() failed. rc=%d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The specified function call failed. It failed with the specified return code. A stack trace was generated."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-FUNCFAIL

SEVERITY: Warning
FORMAT: "%s() RTM subsystem call to %s() failed. rc=%d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The specified function call failed. It failed with the specified return code."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-PARMOUTOFRANGE

SEVERITY: Warning
FORMAT: "%s() Parm %s '%d' is out of range %d-%d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function is out of the specified range of values."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-MALLOCFAILED

SEVERITY: Warning
FORMAT: "%s() Call to ssiMalloc() failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A call to allocate more memory has failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-OPEN_TRANS_FAIL

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

RTM-5-BIND_TRANS_FAIL

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

RTM-5-CNTP_MSGSEND_FA

SEVERITY: Warning
FORMAT: "%s() cntpMsgSend(Queue %s, ptr 0x%x len=%d) failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Attempt to send a control point message buffer failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-CNTP_MSGRECV_FA

SEVERITY: Warning
FORMAT: "%s() cntpMsgRecv(Queue %s) failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Attempt to receive a control point message buffer failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-DB_INIT_FAIL

SEVERITY: Warning
FORMAT: "Initialization of the RTM Database failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Initialization of the SNMP RTM Database failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-INVALID_SRM_SLO

SEVERITY: Warning
FORMAT: "%s() Invalid SRM slot %d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invocation of a function using an invalid SRM slot."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-UNKNOWN_CARD_TY

SEVERITY: Warning
FORMAT: "%s(slot %d, trap %d, seq %d) %s 0x%X."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to generate a trap resulted in an error. The card type of the originating slot could not be identified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-INVALID_VARBIND

SEVERITY: Warning
FORMAT: "%s() Invalid Varbind type %d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An invalid varbind was detected during processing."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-CNTP_SEMCREATE_

SEVERITY: Warning
FORMAT: "%s() cntpSemBCreate() failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Attempt to create the control point semaphore failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-CNTP_SEMTAKE_ER

SEVERITY: Warning
FORMAT: "%s() cntpSemBTake(BasisTrapSem 0x%x) failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Attempt to take the control point semaphore failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-CNTP_SEMGIVE_ER

SEVERITY: Warning
FORMAT: "%s() cntpSemBGive(BasisTrapSem 0x%x) failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Attempt to give the control point semaphore failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-CNTP_MSGBUFTAKE

SEVERITY: Warning
FORMAT: "%s() cntpMsgBufTake(dataLn=%d) failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Attempt to take a control point message buffer failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-7-TRAPS_NOT_ALLOW

SEVERITY: Information
FORMAT: "%s() Trap dropped because they are disallowed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempted trap generation was disallowed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-6-TRAPLOG_WRAP

SEVERITY: Notice
FORMAT: "RTM Trap log wrapped around."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The RTM trap log buffer has wrapped around."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-6-RPM_PORT_CLOSED

SEVERITY: Notice
FORMAT: "Port for RPM slot=%d already closed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to close an RPM port failed because the port was already closed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-RPM_OPEN_PORT_F

SEVERITY: Warning
FORMAT: "Opening RPM Port %s for slot=%d failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to open an RPM port failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-OPEN_PORT_FAILE

SEVERITY: Warning
FORMAT: "%s() Opening Port %s failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "An attempt to open an IPC port failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-PROCESS_DEQUEUE

SEVERITY: Warning
FORMAT: "%s() Call to process_dequeue(0x%x) failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A call to process_dequeue() failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-CREATE_WATCHED_

SEVERITY: Warning
FORMAT: "%s() Call to create_watched_queue(%s) failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A call to create_watched_queue() failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-CREATE_NAMED_PO

SEVERITY: Warning
FORMAT: "%s() Call to ipc_create_named_port(%s) failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A call to ipc_create_named_port() failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-IPC_GET_PAK_MSG

SEVERITY: Warning
FORMAT: "%s() Call to ipc_get_pak_message() failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A call to ipc_get_pak_message() has failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-IPC_SEND_MSG_FA

SEVERITY: Warning
FORMAT: "%s() Call to ipc_send_message() failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A call to ipc_send_message() has failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-MSG_TOO_SMALL

SEVERITY: Warning
FORMAT: "%s() Message of len %d was rejected as too small."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A message of a given length was considered too small."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-PXM_SOI_INIT_FA

SEVERITY: Warning
FORMAT: "%s() Could not spawn PXM SOI Task."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A message of a given length was considered too small."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-RAM_DB_INIT_FAI

SEVERITY: Warning
FORMAT: "%s() Ram DB initialization failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SNMP Ram DB initialization failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-RAMTBL_REGISTRY

SEVERITY: Warning
FORMAT: "%s() Ram Table %s registration failed."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SNMP Ram Table registration failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-RAM_TBL_STDBY_U

SEVERITY: Warning
FORMAT: "%s() Ram Table 0x%x update failed. Elt = %d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SNMP Ram Table update to the standby failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-DB_UPDATE_BAD_A

SEVERITY: Warning
FORMAT: "%s() Standby update action %d invalid."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Standby Ram update failed. Invalid action requested."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

RTM-5-DB_UPDATE_NUM_E

SEVERITY: Warning
FORMAT: "%s() Standby update start elt %d, num elts %d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Standby update needs has the wrong number of elements."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "control-point"

MIBS-5-SEMCREATE_FAILE

SEVERITY: Warning
FORMAT: "%s_%d Semaphore Create Failed for %s, return value %x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Can not create semaphore that is required to protect MIB functions"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

MIBS-5-SEMTAKE_FAILED

SEVERITY: Warning
FORMAT: "%s_%d Semaphore Take failed for %s, return value %x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Can not take semaphore that is required to protect MIB functions"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

MIBS-5-SEMGIVE_FAILED

SEVERITY: Warning
FORMAT: "%s_%d Semaphore Give failed for %s, return value %x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Can not release semaphore which required to protect MIB functions"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

MIBS-5-SEMTAKE_TASK

SEVERITY: Warning
FORMAT: "%s_%d Semaphore was taken by Task Id %x, Task Name %s."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Can not take semaphore because a timeout has occured and the previous task id that took the semaphore is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

MIBS-5-SEMTAKE_RECOVER

SEVERITY: Warning
FORMAT: "%s_%d Could not recover Semaphore from Task Id %x, Task Name %s."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A time out has occured and the previous task still has the semaphore"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "snmp"

SRAT-4-TASKDELAYERROR

SEVERITY: Error
FORMAT: "%s, %d ssiTaskDelay() error"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Internal error has occured"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

SRAT-4-CRD_STATE_EXPIR

SEVERITY: Error
FORMAT: "%s, %d SNMP_RAT waits for CTC_CD_ACT_PLFM_AVL card state expired, waitcounter = %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Internal error has occured."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

SRAT-4-GENERIC_ERROR

SEVERITY: Error
FORMAT: "%s %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "General Failure."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

DDTS "snmp-sa"

SUBA-4-FAILED_RESOLVE_

SEVERITY: Error
FORMAT: "%d Could not resolve EPID. Error 0x%x."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "EPID resolve failed. Subagent will not be registered."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

SUBA-4-FAILED_CREATE_E

SEVERITY: Error
FORMAT: "%dSubagent EPID Creation failed. Error 0x%x."
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "EPID creation failed. Subagent will not be registered."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

SUBA-4-FAILED_BIND_EPI

SEVERITY: Error
FORMAT: "%d Subagent EPID bind failed, Error 0x%x."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to bind EPID. Subagent will not be registered."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

SUBA-4-FAILED_MALLOC

SEVERITY: Error
FORMAT: "%d Failed to allocate memory for %d bytes. Error 0x%x."
FLAG: No Flag
THROTTLING One Second
EXPLANATION: "Failed 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 Collect output from dsplog, dsprev before notifying TAC.

SUBA-4-FAILED_IPCMSG_A

SEVERITY: Error
FORMAT: "%d ssiIpcMessageAllocate failed. Error 0x%x."
FLAG: No Flag
THROTTLING One Second
EXPLANATION: "Failed to allocate memory for IPC message."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

SUBA-4-FAILED_IPCSEND

SEVERITY: Error
FORMAT: "%d ssiIpcMessageSend Failed. Error 0x%x."
FLAG: No Flag
THROTTLING One Second
EXPLANATION: "Failed to send IPC message. MIB might not be registered/MIB Walk might timeout."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

SUBA-4-IPCDATAPTR_INVA

SEVERITY: Error
FORMAT: "%d Invalid IPC Data Pointer."
FLAG: No Flag
THROTTLING One Second
EXPLANATION: "The pointer to the IPC data is either empty or invalid"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Collect output from dsplog, dsprev before notifying TAC.

SUBA-7-SAREGISTER

SEVERITY: Information
FORMAT: "Subagent is registered."
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "Subagent is registered with master agent."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SUBA-7-SADEREGISTER

SEVERITY: Information
FORMAT: "Subagent is being de-registered %s."
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "Subagent being de-registered due to switchover/reset"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SUBA-7-SASTATECHANGE

SEVERITY: Information
FORMAT: "%d State Change detected for the Subagent."
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "State change detected due to switch over/reset."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SUBA-7-SAREQUEST_FAILE

SEVERITY: Information
FORMAT: "%s Failed due to %s issue."
FLAG: No Flag
THROTTLING Five Seconds
EXPLANATION: "SNMP Request failed. Get will return NO_SUCH_NAME, Set will return GEN_ERROR."
RECOMMENDED ACTION: "Collect information specified in field REQUIRED_INFO and call TAC."
REQUIRED INFO "Collect information using following commands. dsplog -mod MIBS dsplog -mod SNMP dsplog -mod SUBAGENT dsplog -sl <slot number specified in the event>."

SUBA-5-INVALID_TYPE

SEVERITY : Warning
FORMAT : "%d: Invalid message type: expected %d received %d"
FLAG : No Flag
THROTTLING : One Second
EXPLANATION : "The message type received is different than what is expected"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO : Collect output from dsplog, dsprev before notifying TAC.

DDTS "sntp"

SNTP-4-pSntpInitErr

SEVERITY: Error
FORMAT: "%s.\n"
FLAG: Stack Trace
THROTTLING No Throttling
EXPLANATION: "Initization Failed."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO "Issue these command on the prompt
a) dspver
b) dsplogs "

SNTP-7-INFO

SEVERITY: Information
FORMAT: "%s.\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "For Information only"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-7-INFO_D

SEVERITY: Information
FORMAT: "%s. [%d]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "For Information only"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-7-INFO_S

SEVERITY: Information
FORMAT: "%s. [%s]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "For Information only."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-7-INFO_IP

SEVERITY: Information
FORMAT: "%s. ip %s\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "For Information only."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-7-INFO_IPD

SEVERITY: Information
FORMAT: "%s. ip %s [%d]\n"
FLAG: No Flag
THROTTLING One Hour
EXPLANATION: "For Information only. The output will contains IP address and value of index in the server list"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-7-INFO_IPD_RTD

SEVERITY: Information
FORMAT: "%s. ip %s [%d]\n"
FLAG: No Flag
THROTTLING One Hour
EXPLANATION: "For Information only. The output will contains IP address and value of round trip delay"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-7-INFO_IPD_IPD

SEVERITY: Information
FORMAT: "%s. IP_1 %s[%d], IP_2 %s[%d]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "For Information only."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-WARN

SEVERITY: Warning
FORMAT: "%s.\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "It happens when sntp receives unknown message or current server responses with unsync flag on"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-WARN_D

SEVERITY: Warning
FORMAT: "%s. [%d]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-WARN_S

SEVERITY: Warning
FORMAT: "%s. [%s]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-WARN_IP

SEVERITY: Warning
FORMAT: "%s. ip %s\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-WARN_IPD

SEVERITY: Warning
FORMAT: "%s. ip %s [%d]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-WARN_IPD_IPD

SEVERITY: Warning
FORMAT: "%s. ip_1 %s[%d], ip_2 %s[%d]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-ERROR

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

SNTP-5-ERROR_D

SEVERITY: Warning
FORMAT: "%s. [%d]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-ERROR_S

SEVERITY: Warning
FORMAT: "%s. [%s]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-ERROR_IP

SEVERITY: Warning
FORMAT: "%s. ip %s\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-ERROR_IPD

SEVERITY: Warning
FORMAT: "%s. ip %s[%d]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-ERROR_IPD_IPD

SEVERITY: Warning
FORMAT: "%s. ip_1 %s[%d], ip_2 %s[%d]\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-5-ERROR_UNKNOWN_M

SEVERITY: Warning
FORMAT: "receive unknown message %d .\n"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-7-SNTP_CLIENT_RCV

SEVERITY: Information
FORMAT: "Client receive invalid packet. Err%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SNTP-7-SNTP_SERVER_RCV

SEVERITY: Information
FORMAT: "Server receive invalid packet. Err%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "spvc"

SPFM-3-DRVINIT

SEVERITY: Minor Alert
FORMAT: "iosDrvInstall() failed with errno %x, while initing SPFMDRV Driver"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "iosDrvInstall() failed while initing SPFMDRV Driver; FTP access to the SM RAM files may be 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 "On PXM cli take the output of ls C"

SPFM-5-SPFM_WARNING

SEVERITY: Warning
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Warning while processing SPVC stats"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "Collect the output of dsplog -mod SPFM"

SPFM-7-SPFM_INFORMATIV

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

DDTS "pxm-connmgm"

SPI-4-SDRV_PATH_ERR

SEVERITY: Error
FORMAT: "Switch Driver Error %s() glcn %d, error-id %d, error-loc %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "This error gets logged to identify a switch Path related problem. It implies an error while programming the conne- ction on the hardware. "
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_CD_ERR

SEVERITY: Error
FORMAT: "Switch Driver Error %s() error-id %d, error-loc %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "This error indicates error while initializing card level drivers. The card may not be able to come up under such circumstances."
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_VI_ERR

SEVERITY: Error
FORMAT: "Switch Driver Error %s() vi %d, error-id %d, error-loc %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error activating slot level VIs. This may result in loss of traffic going towards slot # = VI no +1"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_QB_ERR

SEVERITY: Error
FORMAT: "Switch Driver Error %s() qbin %d, error-id %d, error-loc %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error while activating or modifying the Qbins. "
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_ERR

SEVERITY: Error
FORMAT: "Switch Driver Error error-id %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error while scaling the Qbin or VI rate"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_CONNREF_ER

SEVERITY: Error
FORMAT: "Switch Driver Error %s() conn ref %d line no %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Error trying to reserve an already reserved connref. This implies that connection was incorrectly committed"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_CONNREF_OU

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d connRef=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Conn Ref out of range error. This will result in the connect- ion not getting programmed"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-5-SDRV_PEER_TX_NO

SEVERITY: Warning
FORMAT: "Switch Driver Error line no %d connRef=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The peer Tx connref wasn't ready when appl (PNNI) bind on an Rx connref. The appl should retry until the Tx conn is setup"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPI-4-SDRV_CONNTYPE_O

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d conn ref=%d conntype=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Conn Type for the connRef is out of range. This would result in connection not getting programmed"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_POOL_FULL

SEVERITY: Error
FORMAT: "Switch Driver Error line no %d rsrc=%d, pool=%p"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Pool is full, so resource could not be returned"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_POOL_EMPTY

SEVERITY: Error
FORMAT: "Switch Driver Error line no %d rsrc = %d, pool=%p"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Pool is empty, so unable to get a resource from the pool. This implies that a connection could not get programmed "
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_RSRC_OUTOF

SEVERITY: Error
FORMAT: "Switch Driver Error line no %d rsrc=%x, start=%x, end=%x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Resource return (or set) to pool is out of range (invalid)"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_RSRC_DUP

SEVERITY: Error
FORMAT: "Switch Driver Error line no %d rsrc=%x, pool=%p"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Resource return (or set) to pool duplicated"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_CONN_CMT

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d connRef=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Conn Ref has been used. This implies an error while program- ming the connection on the hardware"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_CONN_MAP_F

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d conn ref %d conntype %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Error mapping glcns to the connref. This implies that connec- tion could not get programmed"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_PATHADD_FA

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d connRef=%d glcn=%d pathType=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Error while programming the connection path on hardware"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_CONN_NOTCM

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d connRef=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Conn Ref has not been committed, so it cannot be modified"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_PATHCFG_FA

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d connRef=%d glcn=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Path has not been added, so it cannot be modified"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_POOL_CORRU

SEVERITY: Error
FORMAT: "Switch Driver Error line no %d rsrc=%d pool=%p"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The resource pool on Standby PXM is corrupted. This may indi- cate that a connection was not programmed on standby PXM"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_SARLCN_ERR

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d connRef=%d direction=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Unable to get SAR information for a non-SAR conn"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_PATHTYPE_I

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d connRef=%d connType=%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Connref has wrong/invalid pathType. This implies that the connection was not programmed"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_POOLGET_ER

SEVERITY: Error
FORMAT: "Switch Driver Error %s() line no %d connRef=%d connType=%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unable to get resource from the resource pool. This implies that connection was not programmed"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-VISWAPPING

SEVERITY: Error
FORMAT: "Error VI Swapping may not have happened properly for %d and %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "VI was being serviced while QE0 changed the Utopia address"
RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-4-SDRV_MEMALLOC_E

SEVERITY: Error
FORMAT: "Switch Driver Error line no %d."
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error allocating memory during system initialization. Database initialization failed. This may imply that connections did not get added."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

SPI-5-SDRV_OUTOF_CONN

SEVERITY: Warning
FORMAT: "Switch Driver Error line no %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Can't allocate a connRef. This may be due no resources (connRef, available"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPI-5-SDRV_OUTOF_ROOT

SEVERITY: Warning
FORMAT: "Switch Driver Error line no %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Can't allocate a Root resource. This may be due no Root resources available"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPI-5-SDRV_OUTOF_LEAF

SEVERITY: Warning
FORMAT: "Switch Driver Error line no %d, mce no %d, root no %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Can't allocate a Leaf resource. The maximum leaf per root should be 12"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPI-5-SDRV_INVALID_RO

SEVERITY: Warning
FORMAT: "Switch Driver Error line no %d, mce no %d, root no %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid mce or root in R' connref"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "unknown"

SPM-7-SHELFDB_INIT

SEVERITY: Information
FORMAT: "Shelf Archive file header init failed, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to initialize shelf archive file header."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SPM-7-SPM_SMDB_INIT

SEVERITY: Information
FORMAT: "Slot %u Mib %u Archive Init Failed, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to initialize slot archive file."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SPM-4-SPM_EPTDB_BAD

SEVERITY: Error
FORMAT: "SPM database corrupt %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SPM database 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

SPM-7-RM_RAMDB_INIT

SEVERITY: Information
FORMAT: "Resource Mgr Ram DB init failed, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to initialize Resource Ram Database."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SPM-7-SPM_TIMER_ERROR

SEVERITY: Information
FORMAT: "Timer operation error, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to start the timer."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SPM-7-SPM_MEM_ERROR

SEVERITY: Information
FORMAT: "Memory allocation error, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to allocate memory."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SPM-7-SPM_MSG_ERROR

SEVERITY: Information
FORMAT: "Message send failed, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to send message."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SPM-7-SPM_ERR_GEN

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "General error."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SPM-4-RM_API_ERROR

SEVERITY: Error
FORMAT: "%s %d %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "RM Api parameter 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

SPM-4-RM_NULL_PTR

SEVERITY: Error
FORMAT: "%s is NULL"
FLAG: Stack Trace | Dump Trace
THROTTLING One Tick
EXPLANATION: "NULL pointer in RM API."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO No Required Info

DDTS "unknown"

SPM-7-SPM_SHELFDB_INI

SEVERITY: Information
FORMAT: "Shelf Archive file header init failed, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to init shelf archive file header"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPM-7-SPM_SMDB_INIT

SEVERITY: Information
FORMAT: "Slot %u Mib %u Archive Init Failed, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to init slot archive file"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPM-2-SPM_EPTDB_BAD

SEVERITY: Major Alert
FORMAT: "SPM database corrupt %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SPM database corruption"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPM-7-SPM_RM_RAMDB_IN

SEVERITY: Information
FORMAT: "Resource Mgr Ram DB init failed, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to init Resource Ram Database"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPM-7-SPM_TIMER_ERROR

SEVERITY: Information
FORMAT: "Timer operation error, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to operate timer"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPM-7-SPM_MEM_ERROR

SEVERITY: Information
FORMAT: "Memory allocation error, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to allocate memory"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPM-7-SPM_MSG_ERROR

SEVERITY: Information
FORMAT: "Message send failed, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to send message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPM-7-SPM_TASK

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

DDTS "spvc"

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in SPVC Finite State Machine event handling The meaning of the string is given below x. soft_master_act0102 Fail to allocate leg record(%d,%d,%d) - Failed to allocate one of connection management data structure for SPVC Master endpoint First parameter Logical id of interface Second parameter vpi Third parameter vci
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-4-SWERROR

SEVERITY: Error
FORMAT: "SOFTWARE ERROR <%d> %d %d %d %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The meaning for variables in the FORMAT string is given below First parameter can be one of following values:
3001 : Connection Management data structure scalling error \
3002 : Error n upping and downing connection \
3003 : Connetion backward bandwidth error \
3004 : Connetion forward bandwidth error \
3005 : NSAP Index error \
3006 : Resync database error \
Second parameter : Logical id of interface \
Third parameter : vpi \
Fourth parameter: vci \
Fifth Parameter : Not used "
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in SPVC route optimization - place holder for future use"
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in SPVC Redundancy Management - place holder for future use"
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in SPVC Configurations - place holder for future use "
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in processing Interfaces/ports failure The meaning for the FORMAT string is given below x. %s() expandSvcRecord Failed pepPtr=%x <%lx %d.%d> - failed to expand SVC records first parameter function name second parameter pointer to SPVC persitent end point data structure Third parameter Interface logical id. Fourth parameter vpi Fifth parameter vci
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in SPVC PEP redundancy The meaning for the FORMAT string is given below x. spvcRedmanJrnlItf invalid Event %d - Invalid event detected
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in handling sig API by SPVCM The meaning of the FORMAT string is given below
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVM-5-WARNING

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

SPVM-7-INFO

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

SPVM-7-DINFO

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

SPVM-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in handling SPVC Manager Events The meaning of the FORMAT string is given below
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVM-7-COMMAND

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Place holder for future use"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in handling SPVC Connection Management Events The meaning of the FORMAT string is given below
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in SPVC and SVC cross check End-point not found for vpi%d, vci%d on interface0x%x first parameter vpi second Parameter vci third parameter Logical id of interface "
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-5-WARNING

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

SPVC-7-INFO

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

SPVC-7-DINFO

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

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in handling SPVC DCMP messages The meaning for the FORMAT string is given below
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Place holder for future use"
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

SPVC-4-ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in Priority Routing This can happen if enqueue/dequeue into priority routing queues fail"
RECOMMENDED ACTION: Issue these comamnds on the shell prompt
a) dspver
b) dsplogs
c) dsperrs
d) dsppnports
e) dspcons
f) dspcon
REQUIRED INFO Collect output of these CLIs
a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons
f) dspcon for connection in problem

DDTS "srm"

SRM-7-SRM_SYNCRAM

SEVERITY: Information
FORMAT: "Event %s received from syncRamManager for DbId %s"
FLAG: No Flag
THROTTLING No Throttling
EXPLANATION: "Information about the Syncram for SRM"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-4-SRM_SYNCRAM_UPD

SEVERITY: Error
FORMAT: "RAM DB update failed for Standby SRM in bay%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ERROR SRM Application on standby card failed to process the RAM DB update message received from the active card. The function name printed identifies the database on which the update failed."
RECOMMENDED ACTION: "This is an application error and might happen due to memory corrpution or a defect. Reset the standby card to see whether the error is transient. If the error is not transient, contact Cisco TAC."
REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."

SRM-4-DBTBLINIT_ERR

SEVERITY: Error
FORMAT: "Failed to register SRM Database Table %s, NumElm=%d, ElmSize=%d, Upgrd=0x%p, dwngrd=0x%p"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM Application failed to initialize the specified database table. This is a fatal error and might be due to memory corruption or unsupported upgrade or downgrade path. "
RECOMMENDED ACTION: "Reset the card to check whether the error is transient if not performing an upgrade or downgrade."
REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."

SRM-4-SRMCT_DBREG_ERR

SEVERITY: Error
FORMAT: "Failed to register %s database, type = %d, version= %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Failed to register the SRM TASK database. SRMCT task will not spawn properly."
RECOMMENDED ACTION: "Contact Cisco TAC."
REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."

SRM-4-DBTBLIDINVLD

SEVERITY: Error
FORMAT: "%s Table %s is invalid. Table type=%d, idx =%d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unable to read/update database record because of invalid table ID. SRM Application will not operate correctly."
RECOMMENDED ACTION: "Contact Cisco TAC."
REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."

SRM-4-HS_INVLD_UPDACT

SEVERITY: Error
FORMAT: "Invalid Update Action -SRM Bay %d, startElement %d, numElements %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unable to update ram database because of invalid update action."
RECOMMENDED ACTION: "Contact Cisco TAC."
REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."

SRM-4-HS_INVLD_UPDATE

SEVERITY: Error
FORMAT: "Invalid Elements -SRM Bay %d, startElement %d, numElements %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unable to update ram database because of invalid element/range."
RECOMMENDED ACTION: "Contact Cisco TAC."
REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."

SRM-4-SRMCT_INIT_ERR

SEVERITY: Error
FORMAT: "Init Error %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRMCT Task initialization error. System will not come up. This is often due to database initialization and registration errors."
RECOMMENDED ACTION: "Contact Cisco TAC."
REQUIRED INFO "Execute \"dsplog -mod SRM\" and provide the log to Engineering."

SRM-7-SRMCT_CD_INS

SEVERITY: Information
FORMAT: "Got SRM Card Insert Msg. from PMM, Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Card insertion notification."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-SRMCT_CD_REM

SEVERITY: Information
FORMAT: "Got SRM Card Remove Msg. from PMM, Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Card removal notification."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-SRMCT_BC_INS

SEVERITY: Information
FORMAT: "SRM Back Card inserted or detected, Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Successful back card detection."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-BC_MISSING

SEVERITY: Information
FORMAT: "SRM Back Card missing or failed, Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unable to detect the back card."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-UNKNOWN_STATE

SEVERITY: Information
FORMAT: "SRMCT entered in unknown state. Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM card in unknown state"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-UNKNOWN_SRM

SEVERITY: Information
FORMAT: "Unknown SRM card detected, Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown SRM card detected."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-PIO_INIT_FAIL

SEVERITY: Information
FORMAT: "SrmInit Failed to initialise PIOs, Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "PIO initialization failure."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-CARD_LOOSE

SEVERITY: Information
FORMAT: "Card Loose;BINS and TINS are High. Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM PIOs indicate that the card is not inserted properly."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-XIL_IMG_ID

SEVERITY: Information
FORMAT: "SRM Xilinx IMG ID. for slot %d, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "XIL image encountered."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-XIL_IMG_ERR

SEVERITY: Information
FORMAT: "SRM Xilinx IMG, Slot %d, %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Function that gets XILimage failed."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-XIL_DNLD_FAIL

SEVERITY: Information
FORMAT: "SRM Xilinx download failed, Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM XILINX down failed."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-FPGA_LOAD_FAIL

SEVERITY: Information
FORMAT: "SRM FPGA load failed, Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM FPGA load failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRM-7-NVRAM_CHECKSUM_

SEVERITY: Information
FORMAT: "SRM NvRam failed. Checksum Error , Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM NvRam failed. Checksum Error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRM-7-SRMCT_FAIL_MSG

SEVERITY: Information
FORMAT: "Received FAIL msg. from SRBM/SRME Task., Slot %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM card failure message received."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-INVALID_MSG

SEVERITY: Information
FORMAT: "SrmMsgHandler Rcvd. Invalid request"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid SRM message received."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-CLR_SRM_CNF

SEVERITY: Information
FORMAT: "Cleared SRM configuartion for bay %d,"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Successfully cleared SRM configuration."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-CLR_SRM_CNF_ERR

SEVERITY: Information
FORMAT: "Error clearing SRM config for bay %d, error %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Error in clearing SRM configuration."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRM-4-SRM_HW_UNSUPPOR

SEVERITY: Error
FORMAT: "SRM CARD FAILED bay = %d, HWREV= %x %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM CARD went in to FAIL state because the hardware revision is not supported."
RECOMMENDED ACTION: "Contact Cisco TAC for information about supported SRM hardware revisions."
REQUIRED INFO "Note down the HWREV printed in this message."

SRM-7-LEGACY_ERR_RPT

SEVERITY: Information
FORMAT: "Srbm Error Rpt %s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Srbm (SRM-3T3) error has occured."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-7-SRME_ERR_RPT

SEVERITY: Information
FORMAT: "Srme Error Rpt %s %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Srme error has occured."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRM-7-IPC_ERR

SEVERITY: Information
FORMAT: "Srm IPC Error Rpt %s, errno = 0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Srm IPC error has occured. Can be ignored during graceful-upgrades or if PXM/SRM is not redundantly configured."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

SRM-7-SRME_UNKNOWN_CL

SEVERITY: Information
FORMAT: "SRME Clock driver Error Rpt %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRME Clock driver Error has occured. Assuming Semtech Clock chip."
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SRM-4-ONLINE_DIAG_ERR

SEVERITY: Error
FORMAT: "SRM online diagnostic error Error %s, %d, 0x%x, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM/SRME Online diag error has occured."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the output of CLIs dspver, dspcds, dsplog

SRM-4-OFFLINE_DIAG_ER

SEVERITY: Error
FORMAT: "srm offline diag error %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SRM/SRME Offline Diag not supported"
RECOMMENDED ACTION: No action required
REQUIRED INFO "No information required"

SRM-7-RAM_SYNC_IOV_FA

SEVERITY: Information
FORMAT: "Call to %s returned error, ramDbId=0x%x"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "tRed Ram Sync message create and sending errors"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "atmsig"

SSCO-4-SSCOP_NOMEM_WAR

SEVERITY: Error
FORMAT: "SSCOP/%s;Out of Mem for%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Required Memory/IPC buffer could not be allocated for the subsystem\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_NOBUF_WAR

SEVERITY: Error
FORMAT: "SSCOP/%s;Out of IPC Buf for%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Required IPC buffer could not be allocated for the subsystem\n"
RECOMMENDED ACTION: This is a temporary condition. If the error message continues to appear, please 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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_NOMEM_MAJ

SEVERITY: Error
FORMAT: "SSCOP/%s;Out of Mem for%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Required Memory could not allocated during system init time\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information:
1) On the PXM/PXM45 Controller Card CLI execute the following commands and capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_CBPOOL_IN

SEVERITY: Error
FORMAT: "SSCOP/%s;Cb pool init fail\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Internal memory pool initialization failed during system init time\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_SRCHHELPE

SEVERITY: Error
FORMAT: "SSCOP/%s;Search helper init fail\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Required Memory could not allocated during system init time\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_EP_CREAT_

SEVERITY: Error
FORMAT: "SSCOP/%s;EP creat fail for%s\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Internal IPC endpoints can not be created during system init time\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-2-SSCOP_STG1_INIT

SEVERITY: Major Alert
FORMAT: "SSCOP/%s;Stage1 init fail\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Stage1 initialization of internal task structures failed\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-3-SSCOP_INIT_FAIL

SEVERITY: Minor Alert
FORMAT: "SSCOP/%s;Init failed\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Task initialization failed\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_CBPOOL_HN

SEVERITY: Error
FORMAT: "SSCOP/%s;Cb pool handl err;Reason%s\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Un-initialized or null handle in the internal data structure\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_TMRLIB_ER

SEVERITY: Error
FORMAT: "SSCOP/%s;Tmr lib err;Reason%s\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Timer library initialization error\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_NULLPTR

SEVERITY: Error
FORMAT: "SSCOP/%s;Null ptr%s\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Invalid address error\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-7-SSCOP_NULLCTLBL

SEVERITY: Information
FORMAT: "SSCOP/%s;Null Cb;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Control Blk Could not be accessed with the given logical port id\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_NULLIDB

SEVERITY: Error
FORMAT: "SSCOP/%s;Null idb;Itf Id%d;cb ptr0x%x\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Control Block has invalid interface block address\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-6-SSCOP_VCUPMSG

SEVERITY: Notice
FORMAT: "SSCOP/%s;Vc Up Msg Rcvd;Itf Id%d;tx Lcn%d;rx Lcn%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A VC UP message is received; (Event Not in Use)\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_VCDOWNMSG

SEVERITY: Notice
FORMAT: "SSCOP/%s;Vc Dn Msg Rcvd;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "A VC DOWN message is received; (Event Not in Use)\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-4-SSCOP_VCBINDFAI

SEVERITY: Error
FORMAT: "SSCOP/%s;LCN bind failed;Itf Id%d;Lcn%d\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "LCN could not be attached to IPC endpoint\n"
RECOMMENDED ACTION: This is a temporary condition. If the error persists and if the error prevented the SSCOP protocol establishment on the corresponding port for which the error is reported and it the port is configured to run SSCOP protocol, copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-4-SSCOP_CTLBLK_IN

SEVERITY: Error
FORMAT: "SSCOP/%s;Err in cb insert for itf Id%d\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Control Block could not be added to internal datastructure\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_CTLBLK_DE

SEVERITY: Error
FORMAT: "SSCOP/%s;Err in cb del for itf id%d;delr_p%p;dela_ptr%p;Reason%s\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Control Block could not be deleted from internal datastructure\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-4-SSCOP_WAVL_DEL_

SEVERITY: Error
FORMAT: "SSCOP/%s;Err in cb del for cb for itf id%d;Thread%d;Reason%s\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Control Block could not be deleted from internal datastructure\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_CLR_EPID

SEVERITY: Error
FORMAT: "SSCOP/%s;Epid(s) clear;Reason%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Delete IPC endpoint(s) due to error in IPC endpoint(s) creation\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-6-SSCOP_INTF_ADD

SEVERITY: Notice
FORMAT: "SSCOP/%s;Cb addition success;itf id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Control Block addtion Successful; (Event not in use) \n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-4-SSCOP_INTF_TXQ_

SEVERITY: Error
FORMAT: "SSCOP/%s;TxQ Init fail;itf id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Internal Q initialization error\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-6-SSCOP_INTF_EXIS

SEVERITY: Notice
FORMAT: "SSCOP/%s;Itf exists;Itf Id%d \n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Duplicate SSCOP add request for an existing interface\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_INTF_NOT_

SEVERITY: Notice
FORMAT: "SSCOP/%s;Itf not exists;Cb not deleted;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Delete SSCOP req received for an non-existing interface\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_INTF_DEL

SEVERITY: Notice
FORMAT: "SSCOP/%s;Cb del success;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP interface deletion successful\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-4-SSCOP_OPENFAIL

SEVERITY: Error
FORMAT: "SSCOP/%s;Err in prot open;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP protocol open error; (Event not in use)\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-4-SSCOP_CLOSEFAIL

SEVERITY: Error
FORMAT: "SSCOP/%s;Err in prot close;Itf Id%d\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "SSCOP protocol close error;\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-5-SSCOP_VCUNBINDF

SEVERITY: Warning
FORMAT: "SSCOP/%s;Lcn unbind Fail;Itf Id%d;Lcn%d\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "IPC Endpoint LCN unbind error\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-4-SSCOP_FREE_LIST

SEVERITY: Error
FORMAT: "SSCOP/%s;Cb enq onto free lst fail;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Addition into internal free list failed\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-6-SSCOP_FREE_LIST

SEVERITY: Notice
FORMAT: "SSCOP/%s;Cb 0x%x enq'd to free lst;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Control Block is enqueued to free list (Event not in use)\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-4-SSCOP_CNF_FAIL

SEVERITY: Error
FORMAT: "SSCOP/%s;Cfg chg incomplete;Cmd%s;Reason%s;Itf id%d\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Configuration command could not be successfully completed\n"
RECOMMENDED ACTION: Retry the configuration request again. If the error persists copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_UNKNOWN_S

SEVERITY: Error
FORMAT: "SSCOP/%s;Unknown ssi msg;Msg Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown IPC message received\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_UNKNOWN_E

SEVERITY: Error
FORMAT: "SSCOP/%s;Unknown Evt;Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unknown internal event\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_IPC_SEND_

SEVERITY: Error
FORMAT: "SSCOP/%s;IPC snd fail;From %s tsk to epid 0x%x;Msg Ptr 0x%x;SSI ErrNo0x%x;Msg Type0x%x\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "IPC send failure\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_INV_PAK

SEVERITY: Error
FORMAT: "SSCOP/%s;Inv Pak;Reason%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Internal IPC message conversion failed\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_INV_SSCOP

SEVERITY: Error
FORMAT: "SSCOP/%s;Inv SSCOP Version 0x%x;Result%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid SSCOP protocol version detected; (Event not in use)\n"
RECOMMENDED ACTION:
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-6-SSCOP_RESOLV_EP

SEVERITY: Notice
FORMAT: "SSCOP/%s;Resolve incomplete for Ep%s\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Peer tasks IPC endpoint can not be resolved\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_INIT_CB

SEVERITY: Error
FORMAT: "SSCOP/%s;InitSscopCb;Itf id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP control Block is initialized (Event not in use)\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-6-SSCOP_TMR_EXP

SEVERITY: Notice
FORMAT: "SSCOP/%s;Tmr 0x%x Expiry;Itf Id%d;State0x%x\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Timer Expired (Event no in use)\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-4-SSCOP_TMR_EXP_E

SEVERITY: Error
FORMAT: "SSCOP/%s;Tmr 0x%x expires wrongly;Itf Id%d;State 0x%x\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Timer expiry in wrong state\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-4-UNEXPECTEDTIMER

SEVERITY: Error
FORMAT: "SSCOP/%s;Unknown tmr expiry;tmr0x%x;type%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unexpected timer (Event not in use)\n"
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 following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-6-SSCOP_LINK_EST

SEVERITY: Notice
FORMAT: "SSCOP/%s;SSCOP LNK EST;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP Link is established\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_LINK_REL

SEVERITY: Notice
FORMAT: "SSCOP/%s;SSCOP LNK REL;Itf Id%d st%d Rsn%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP Link is released;\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_LINK_RST

SEVERITY: Notice
FORMAT: "SSCOP/%s;SSCOP LNK RST;Itf Id%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP link is reset;\n"
RECOMMENDED ACTION:
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-4-SSCOP_SEQ_ERR

SEVERITY: Error
FORMAT: "SSCOP/%s;Err%d;Info%d;port%d;Str%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP protocol sequence error detected \n"
RECOMMENDED ACTION:
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-5-SSCOP_PEER_VER_

SEVERITY: Warning
FORMAT: "SSCOP/%s;Verify peer UNI ver;Info%s\n"
FLAG: No Flag
THROTTLING One Minute
EXPLANATION: "Peer equipment appears to run an old version of ATM UNI\n"
RECOMMENDED ACTION:
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-5-SSCOP_PEER_VER_

SEVERITY: Warning
FORMAT: "SSCOP/%s;Verify Peer UNI ver;Info%s\n"
FLAG: No Flag
THROTTLING One Minute
EXPLANATION: "Peer equipment is appears to run an higher version of ATM UNI\n"
RECOMMENDED ACTION:
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-6-SSCOP_INIT

SEVERITY: Notice
FORMAT: "SSCOP/%s;Prot init;Itf id%d;state %s;Info%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP Control Block is initialized\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-4-SSCOP_PROV_REBU

SEVERITY: Error
FORMAT: "SSCOP/%s;Rebuild Err;Reason%s;Itf id%d\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Provisioning data rebuild error\n"
RECOMMENDED ACTION:
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-6-SSCOP_TASK_ST_C

SEVERITY: Notice
FORMAT: "SSCOP/%s;Tsk st chg;Prev st%s;Curr St%s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "SSCOP task changed state\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_TASK_WRON

SEVERITY: Notice
FORMAT: "SSCOP/%s;Tsk rcvd wrong evt0x%x;St0x%x\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Unexpected task change event received\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_TMR_FATAL

SEVERITY: Error
FORMAT: "SSCOP/%s;Tmr start error;Tmr0x%x\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Timer start error\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_TMR_STOP_

SEVERITY: Error
FORMAT: "SSCOP/%s;Tmr stop error;Tmr0x%x\n"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Timer Stop Error \n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_CONGAPI_E

SEVERITY: Error
FORMAT: "SSCOP/%s;Cong API Err;ID0x%x;Info10x%x;Info20x%x\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Internal congestion API error\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

SSCO-4-SSCOP_HIRESND_R

SEVERITY: Error
FORMAT: "SSCOP/%s;Toomany resnd req;port%d;Seqno%d;RsndCnt%d;maxRsndCnt%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Peer is requesting to resend the same PDU too many times\n"
RECOMMENDED ACTION:
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number> dspsscop <port_id>; "port_id" is the port id of interface with the problem dsppnilmi <port_id>; "port_id" is the port id of interface with the problem dsppnctlvc <port_id>; "port_id" is the port id of interface with the problem

SSCO-6-SSCOP_DBGLOG

SEVERITY: Notice
FORMAT: "SSCOP/%s;\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Useful debug information\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_DUP_VCUP_

SEVERITY: Notice
FORMAT: "SSCOP/%s;Itf exists;NoLcnChg;Itf Id%d oldRx%d oldTx%d newRx%d newTx%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Received a duplicate VC UP message with No LCN change\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_DUP_VCUP_

SEVERITY: Notice
FORMAT: "SSCOP/%s;Itf exists;LcnChg;Itf Id%d oldRx%d oldTx%d newRx%d newTx%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Received a VC UP message for an already UP port but with different LCNs\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_VC_BIND_M

SEVERITY: Notice
FORMAT: "SSCOP/ VC_BIND_MSGOn port %d rx lcn %d tx lcn %d %s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Received VC BIND message\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_VC_UNBIND

SEVERITY: Notice
FORMAT: "SSCOP/ VC_UNBIND_MSGOn port %d rx lcn %d tx lcn %d %s\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Received VC UNBIND message\n"
RECOMMENDED ACTION: No action required
REQUIRED INFO No Required Info

SSCO-6-SSCOP_INVALID_V

SEVERITY: Notice
FORMAT: "SSCOP Func%s; Var%s;Val%x;Loc%d\n"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Invalid param value in sscop\n"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, e-mail your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO Please collect the following information
1) On the PXM/PXM45 Controller Card CLI execute the following commands and
capture the outputs into a file dspver dspcds dspdate dsppnports dsplog dsperr -sl <slot_number>

DDTS "ssi"

DTAP-4-INVALID_CONID

SEVERITY: Error
FORMAT: "%s Invalid Connection ID (0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer API error Input Connection/Transfer ID 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 for specified slot and the specified error number."

DTAP-5-TOOMANYCONS

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

DTAP-5-INVALID_CONNAME

SEVERITY: Warning
FORMAT: "%s The name string (%d) is either 0 or too long (Max %d )"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer API error Connection Name exceeds the maximum allowed or is name length is zero"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DTAP-5-INVALID_PARM

SEVERITY: Warning
FORMAT: "%s Parameter %s has invalid value 0x%x (transferId 0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer API error one of the input parameters has an invalid value assigned to it"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DTAP-5-INVALID_DATALEN

SEVERITY: Warning
FORMAT: "%s Invalid data length %d (Max %d) (transferId 0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer API error "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DTAP-4-INVALID_BUFFER

SEVERITY: Error
FORMAT: "%s Invalid data buffer 0x%x (0x%x) (transferId 0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer API error Send/Receive/Alloc message buffer is NULL or has bad magic"
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 for specified slot and specified error number."

DTAP-5-INVALID_RECVAPI

SEVERITY: Warning
FORMAT: "%s Invalid API - handler already attached (transferId 0x%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer API error Receive function (EPID handler) has been registered for this connection ID, this makes call to ssiDataTransferReceive() is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DTAP-5-INVALID_REREG

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

DTAP-5-INVALID_MSGSIZE

SEVERITY: Warning
FORMAT: "%s Invalid size (%d) exceeds the maximum allowed size (%d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer API error Message size parameter exceeds the maximum allowed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DTAP-5-INVALID_EPID

SEVERITY: Warning
FORMAT: "%s Invalid EPID in DB Table Entry for DBID (%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Failed to get EPID The communication endpoint for this app."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DTAP-5-FAILED_ALLOC

SEVERITY: Warning
FORMAT: "%s Data Allocation of size (%d) failed"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Data Transfer API error Failed to allocate buffer "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DTAP-5-FAILED_PROTOEVT

SEVERITY: Warning
FORMAT: "%s Protocol Event (%d) failed for conId (%x)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer API error Failed to reset the protocol for a a connection."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DTAP-5-INVALID_FUNC

SEVERITY: Warning
FORMAT: "%s Function is not implemented"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Data Transfer API error Function not implemented"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

DDTS "ssi"

FAS-5-SEMTAKE

SEVERITY: Warning
FORMAT: "ssiSemTake failed for %s with errno %x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "FAS API failed to get fasLfdSem semaphore, hence cannot access file descriptor table"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-2-SEMGIVE

SEVERITY: Major Alert
FORMAT: "ssiSemGive failed for %s with errno %x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "FAS API failed to give fasLfdSem semaphore, hence Remote file access will be frozen"
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 "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
On slot where it happened
1. dspsems
2. dspsem <semId of fasLfdSem, 1>
3. dsptasks
4. dsptask (taskId holding semaphore, level)"

FAS-4-FDINVALID

SEVERITY: Error
FORMAT: "File descriptor (%d) is invalid"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "File descriptor supplied by the application is invalid"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dsptasks"

FAS-4-MAXSZTOOSMALL

SEVERITY: Error
FORMAT: "Max Data Transfer Size (%d) is <= FAS Header size (%d)"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "The Max Data Transfer Size obtained from Data Transfer Module is lesser or equal to the FAS request/response header size. So, no buffer for FAS Data."
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 "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dsptasks"

FAS-5-NOTREADY

SEVERITY: Warning
FORMAT: "File access server is not ready. Semophore %s not initialized"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "File access server is not initialized. Cannot use remote access API yet"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-3-FDFULL

SEVERITY: Minor Alert
FORMAT: "Remote file descriptor table is full. Total being used %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Remote file descriptor table is full. Too many remote file transfers happening"
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 "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dsptasks"

FAS-3-REQUNKNOWN

SEVERITY: Minor Alert
FORMAT: "File access server(version %d) received unknown request %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "File access server received unknown request. Protocol 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 "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dsptasks"

FAS-5-DTINUSE

SEVERITY: Warning
FORMAT: "This file transfer conection(%x) is already in use"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Present FAS data transfer connection is already doing a file transfer. Another file open request received"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-4-PARAMINVALID

SEVERITY: Error
FORMAT: "Application supplied an invalid parameter %s"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Application supplied an invalid parameter. Cannot proceed with the API call"
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 "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dsptasks"

FAS-5-TIDINVALID

SEVERITY: Warning
FORMAT: "Data Transfer returned invalid param %x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Data Transfer returned invalid param in the callback routine"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-WARNING

SEVERITY: Warning
FORMAT: "line %d, errno 0x%x, errMsg %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "General warnings"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-WRVER

SEVERITY: Warning
FORMAT: "Protocol version mismatch, expected %d, got %d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "FAS Protocol version mismatch. Cannot handle received message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-1-CTCDBLD

SEVERITY: Fatal
FORMAT: "ctcApplGotoDbBuildState() failed with errno%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ctcApplGotoDbBuildState() failed. Cannot start FAS application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dspsems
6. dsptasks"

FAS-1-CTCDBSYNC

SEVERITY: Fatal
FORMAT: "ctcApplGotoDbSyncState() failed with errno%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ctcApplGotoDbSyncState() failed. Cannot start FAS application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dspsems
6. dsptasks"

FAS-1-CTCGOREADY

SEVERITY: Fatal
FORMAT: "ctcApplGotoRdyState() failed with errno%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ctcApplGotoRdyState() failed. Cannot start FAS application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dspsems
6. dsptasks"

FAS-5-IPWAIT

SEVERITY: Warning
FORMAT: "ssiIpcComEpWait() returned with errno%d"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "ssiIpcComEpWait() returned. Going back to ssiIpcComEpWait()"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-1-SEMCREATE

SEVERITY: Fatal
FORMAT: "ssiSemCreate failed for %s with errno %x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "FAS API failed to create fasLfdSem semaphone, hence Remote file server will be frozen"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dspsems
6. dsptasks"

FAS-1-EVTHDLR

SEVERITY: Fatal
FORMAT: "FAS ctcEventHandler callback returning error %x, for eventtype %x, in routine %s return code %x"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "FAS ctcEventHandler failed to act on the received 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 "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dsptasks"

FAS-2-DRVINIT

SEVERITY: Major Alert
FORMAT: "iosDrvInstall() failed with errno %x, while initing FAS Driver"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "iosDrvInstall() failed while initing FAS Driver; FTP access to the SM RAM files may be 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 "On PXM
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dspsems
6. dsptasks"

FAS-2-DEVADD

SEVERITY: Major Alert
FORMAT: "iosDevAdd() failed with errno %x, for logical partition '%s'"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "iosDevAdd() failed for a logical partition. FTP access to that partition may be 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 "Capture the output from
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. dspsems
6. dsptasks"

FAS-5-READOP

SEVERITY: Warning
FORMAT: "Read dir op is not supported by this FAS driver"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Read dir op is not supported by this FAS driver"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-LOGPART

SEVERITY: Warning
FORMAT: "Logical partition %s not found in the table"
FLAG: Stack Trace
THROTTLING One Tick
EXPLANATION: "Logical partition not found in the FAS partitions table. The requested partition cannot be accessed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-DEVNM

SEVERITY: Warning
FORMAT: "Device Name too long %s "
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "The request to access a directory found the directory name to exceed valid directory length."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-BDINPUT

SEVERITY: Warning
FORMAT: "Failed to process access to STBY %s - %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Access to STBY disk rejected due to invalid parameters."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-BDSTBYSLOT

SEVERITY: Warning
FORMAT: "Failed to process access to STBY slot number error from ctc"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "Access to STBY disk rejected due to invalid slot number from CTC application"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-DIOFILELOCKTAKE

SEVERITY: Warning
FORMAT: "line %d, errno 0x%x, lock type %d, timeout %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiDIOFileLockTake() failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-DIOOPEN

SEVERITY: Warning
FORMAT: "line %d, errno 0x%x, name %s, flags %d, mode %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiDIOOpen() failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-DIOCOPY

SEVERITY: Warning
FORMAT: "line %d, errno 0x%x, from %s, to %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiDIOCopy() failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-IPCMSGALLOC

SEVERITY: Warning
FORMAT: "line %d, errno 0x%x, size %d, priority %d"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiIpcMessageAllocate() returned NULL"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-5-DATAXFERMSGALLO

SEVERITY: Warning
FORMAT: "line %d, errno 0x%x, size %d, errMsg %s"
FLAG: No Flag
THROTTLING One Tick
EXPLANATION: "ssiDataTransferMsgAlloc returned NULL"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO No Required Info

FAS-7-INFO