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

LMI-5-GEN_ERR

Table Of Contents

LMI-5-GEN_ERR

LMI-5-CTC_STATE_ERR

DDTS "unknown"

LSM_-7-FBALLOC_FAIL

LSM_-7-MSGSND_ERROR

LSM_-7-MSG_PROC_ERR

DDTS "snmp-ma"

MAST-7-INFO

MAST-7-MSG_INVALID

MAST-7-CONNECT

MAST-4-RTM_CREATE_FAIL

MAST-4-RTM_SEMTAKE_FAI

MAST-4-RTM_SEMGIVE_FAI

MAST-4-FAILED_INIT

MAST-4-FAILED_CONFIG

MAST-4-FAILED_DBCREATE

MAST-4-FAILED_TBLCREAT

MAST-4-FAILED_DBREGIST

MAST-4-FAILED_DBUPDATE

MAST-4-FAILED_DBREAD

MAST-4-FAILED_MALLOC

MAST-4-FAILED_IPCMSG_A

MAST-4-SUBAGENT_NOTEXI

MAST-4-OPEN_TRANSPORT

MAST-4-SENDTO_TRANSPOR

MAST-4-BIND_TRANSPORT

MAST-4-FAILED_IPCSEND

MAST-4-FAILED_FUNCTION

MAST-4-EVENT_INVALID

MAST-4-IPCDATAPTR_INVA

MAST-6-T_CREATE

MAST-6-METHOD

MAST-6-DISCARD

MAST-6-BURST

MAST-6-SA_REG_SEQ

MAST-6-SA_REG_MSG_LOST

MAST-5-WARNING

MAST-4-SADISCONNECT

MAST-7-SAREGISTER

MAST-7-SADEREGISTER

MAST-7-TBLOCKFAILED

MAST-4-CNFSNMP_ERRORMI

MAST-4-CNFSNMP_IPCREPL

MAST-4-CNFSNMP_ERRORPA

MAST-4-FAILED_DBUPD_RE

MAST-5-LARGE_TRAPSIZE

MAST-5-INVALID_PARAM

DDTS "snmp-ma"

MIB-4-MEMALLOCFAILED

MIB-7-UNKNOWNFRONTMOD

MIB-7-UNKNOWNLINEMODU

MIB-7-NOENTPHYSINDEX

MIB-7-NOENTITYFOUND

MIB-7-INVALID_INDEX_E

MIB-7-INVALID_THRESH_

MIB-7-INVALID_ENTITY_

MIB-7-MAX_THRESH_INDE

MIB-7-INDEX_ENTRY_EXC

MIB-7-NULL_POINTER_FO

MIB-7-UNKNOWN_PHYSICA

MIB-7-ENTITY_TABLE_AD

MIB-7-ENTITY_TABLE_UP

MIB-7-SHM_UPDATE_ERRO

MIB-7-INVALID_SHM_ENT

MIB-7-GET_SENSOR_THRE

MIB-7-INVALID_ENTITY_

MIB-7-ENTITY_TABLE_EX

MIB-7-UNEXPECTED_CONT

DDTS "ccma"

OAM-4-OAMTIMERFAIL

OAM-4-CPRONOTIFYFAIL

OAM-4-LOG

OAM-7-ERROR

DDTS "pnnisys"

ATM-4-UNSUPPORTED_QOS

ATM-4-OUT_OF_VCDS

ATM-5-UNMATCHUNIVERSI

ATM-5-MTUCALLMISMATCH

ATM-4-FAILCREATEVC

ATM-5-ILMIKEEPALIVEFA

ATM-5-ILMICONFIGCHANG

ATM-5-VPIVCIRANGE

ATM-6-ATMSOFTSTART

ATM-7-ILMINOAUTOCFG

ATM-7-ILMIAUTOCFGALRE

ATM-7-ILMINOAUTOCFGAL

ATM-6-ILMIADDREG

ATM-6-ILMIACCFILTER

ATM-6-ILMIDEFACCFILTE

DDTS "atmsig"

ATMS-4-NOSVC

ATMS-4-NOCALLREF

ATMS-4-ATMSIG_SVC_INSE

ATMS-4-ATMSIG_SVC_DELE

ATMS-4-ATMSIG_PRTY_INS

ATMS-4-ATMSIG_PRTY_DEL

ATMS-4-ATMSIG_CUG_INSE

ATMS-4-ATMSIG_CUG_DELE

ATMS-6-FAILHALFLEGREM

ATMS-4-FAILXCONN

ATMS-5-CONFIG_ERROR

DDTS "ipc"

IPC-3-NOMEM

IPC-5-CONSISTENCY

IPC-6-SLAVELOG

IPC-6-NODELFUNC

IPC-3-UNLOCK

IPC-3-LOCK

IPC-3-CANT_SEND

IPC-3-NODISPATCH

IPC-4-DELETED

IPC-3-ONINT

IPC-4-NOBUFF

IPC-4-GIANT

IPC-6-NULL

IPC-6-INVALID

IPC-6-NULLDELFUNC

IPC-3-NO_ACK_HANDLER

IPC-5-GET_PAK_MSG

IPC-6-QFULL

IPC-3-PRECLOSE

IPC-4-INV_CALLBACK

DDTS "ipc"

WATC-4-NOEVENT

SYS-4-MGDTIMER

SYS-4-TIMERNEG

SYS-7-DELETE_IPC_SEAT

DDTS "atmsig"

UTIL-4-TREE

DDTS "alarms"

NAM-5-INVALIDINPUT

NAM-5-PARMOUTOFTRANGE

NAM-5-PARMINVALID

NAM-5-PARMINVLENGTH

NAM-5-SYS_RESPONSE_ER

NAM-5-ALARM_HANDLING

NAM-5-ALARM_HANDLING_

NAM-5-QUEUEFULL

DDTS "atmsig"

NCDT-5-ADD_CLK_SRC_FAI

NCDT-5-DEL_CLK_SRC_FAI

NCDP-5-INVALIDFCNCALL

NCDP-4-NULLPTR

NCDP-4-APINULLPTR

NCDP-5-INVMSGTYPE

NCDP-5-INVALIDCASE

NCDP-5-RCNOTOK

NCDP-5-VALOUTOFRNG

NCDP-5-INVALIDCODEEXEC

NCDP-5-INVALIDCONF

NCDP-5-UNABLETOREACHCL

NCDP-4-CLIBLOCKED

NCDP-4-MALLOCFAIL

NCDP-5-UNEXPECTEDCASE

NCDP-5-ERRORRC

NCDP-5-NAKRSP

NCDP-5-INVALIDLOGICALI

NCDP-5-TRAPIGNORED

NCDP-5-UNKNOWNSLAVE

NCDP-7-INFO_CLOCK

DDTS "atmsig"

NCDT-4-NOMEM_WARN

NCDT-5-NULLPTR

NCDT-6-UNKNOWN_EVT

NCDT-4-IPC_SEND_FAIL

NCDT-5-PORT_INVLD

NCDT-4-ADDVC_FAIL

NCDT-4-DELVC_FAIL

NCDT-4-TX_RX_LCN_NOT_S

NCDT-4-SLAVE_ID_NOTPXM

NCDT-4-TMINIT_FAIL

NCDT-4-TMSTOP_FAIL

NCDT-4-ADD_CLK_SRC_FAI

NCDT-4-DEL_CLK_SRC_FAI

NCDT-5-INVLD_CASE

NCDT-4-GENERAL_ERR_INF

NCDT-7-GENERAL_INFO

NCDT-4-INVALID_ARG

NCDT-7-CLK_TRAP

NCDT-4-DISABLE_PORT

NCDT-5-PORT_MARK_DOWN

NCDT-4-IPC_Q_CREATE_FA

NCDT-4-IPC_Q_ATTACH_FA

NCDT-4-NBSM_NOT_SUPP_T

NCDT-4-FRSM_NOT_SUPP_C

NCDT-4-CLK_SET_NAK

NCDT-4-CLK_UNSET_NAK

DDTS "ncdp"

NCPT-2-MALLOC_FAILURE

NCPT-4-IPC_FAILURE

NCPT-4-DATAPTR_FAILURE

NCPT-4-MSG_SEND_FAIL

NCPT-4-LCN_BIND_FAIL

NCPT-4-LCN_UNBIND_FAIL

NCPT-4-LCN_BINDABLE_ER

NCPT-4-UNKNOWN_PDU

NCPT-4-UNKNOWN_MSG_TYP

NCPT-4-EP_CREATE_ERR

NCPT-4-PORT_SEARCH_FAI

NCPT-4-PORT_INDEX_UNAV

NCPT-5-LOG_WARNING

NCPT-7-LOG_INFORMATIVE

DDTS "boot/shm"

BOOT-4-NULL_PTR

NILE-7-ECHKERR

NILE-7-MCHKERR

NILE-7-WPERR

DDTS "ccma"

OAM-5-LOG

DDTS "unknown"

OAM-7-INIT_SUCCESS

OAM-7-RCV_MSG_FAIL

OAM-7-RCV_CELL_FAIL

DDTS "pxm-connmgm"

PCEM-5-PCEMAERR

PCEM-5-PCEMAERRCODE

PCEM-4-RAMSYNC

PCEM-4-GENERR

PCEM-5-LSLOTINFOERR

PCEM-5-SLOTRESRVERR

DDTS "pxm-connmgm"

PCPR-4-PASSTHROREGFAIL

PCPR-5-INVALIDRATEVENT

PCPR-2-SYNCRAMERR

PCPR-5-PCPROTIMERFAIL

PCPR-6-PCPROTIMERSET

PCPR-4-PCPROMSGHDLRFAI

PCPR-4-PCPRONAMEBINDFA

PCPR-5-IFAUDITFAIL

PCPR-5-CONNAUDITFAIL

PCPR-5-CONNAUDITMISMAT

PCPR-4-COMEPCREATEFAIL

PCPR-4-TASKCREATEFAIL

PCPR-4-TASKDELETEFAIL

PCPR-4-INVALID_CNTRLR_

PCPR-4-SYNCRAMINITFAIL

PCPR-4-CONN_DEL_ERROR

PCPR-4-CONN_ADD_ERROR

PCPR-7-INVALID_CNTRLR_

PCPR-4-RESERVED_CARDTY

PCPR-4-INVALIDSLOT_ERR

PCPR-5-SEM_TIMEOUT

DDTS "shm"

REDM-2-pRedmanInitErr

REDM-2-pRedmanStdbySnd

REDM-1-pRedmanMallocEr

REDM-2-pRedmanInValidS

REDM-2-pRedmanInValidE

REDM-7-pRedmanInfo

REDM-7-pRedmanInfo1

REDM-7-pRedmanRootMsg

REDM-7-pRedmanTblReadE

REDM-7-pRedmanMap

REDM-2-pRedmanMapErr

REDM-7-pRedmanRecNo

REDM-7-pRedmanMaxRec

REDM-7-pRedmanitfDsp

REDM-2-pRedmanIfCbErr

REDM-2-pRedmanItfMapEr

REDM-2-pRedmanDiskErr

DDTS "shm"

PCTC-7-PCTCINIT

PCTC-7-PMMQUERY

PCTC-7-MSGRECV

PCTC-7-MSGSEND

PCTC-7-MSGHANDLE

PCTC-7-MSGTYPE

PCTC-7-MSGDATA

PCTC-7-CONVCGET

PCTC-7-BADPCTCEPID

PCTC-7-BADPMMEPID

PCTC-7-RECVDATA

PCTC-7-WRONGMSG

PCTC-7-STARTSPAWN

PCTC-7-PLATSPAWN

PCTC-7-PLATRAM

PCTC-7-PLATSYNC

PCTC-7-PLATREADY

PCTC-7-APPLSPAWN

PCTC-7-APPLRAM

PCTC-7-APPLSYNC

PCTC-7-APPLREADY

PCTC-7-WRONGSEQ

PCTC-7-WRONGSEQS

PCTC-7-APPLSPAWNFAIL

PCTC-4-EVENTFAIL

DDTS "cema"

PHY-4-PHY_ERR

PHY-5-FRM

DDTS "unknown"

PING-5-PING_WARNING

PING-7-PING_INFORMATIV

DDTS "ipc"

PIPC-4-MAJ_ERR_LOG

PIPC-4-INV_PTR_RCVD

PIPC-4-INVALID_PTR

DDTS "vsi"

VSIC-5-VSICGENERR

VSIC-5-VSICPROTERR

VSIC-5-VSICSYSERR

VSIC-5-VSICINTRNLERR

VSIC-2-VSIMAJORERR

VSIS-5-INFO

VSIS-5-VSISERR

VSIS-5-RAMSYNC

VSIS-5-GENERR

VSIS-5-SCTFAIL

VSI_-5-VSIRMERR

VSI_-5-INFO

VSI_-3-RMCLKFatal

VSI_-4-RMCLKError

VSI_-5-RMCLKWarning

VSI_-3-RMSYSFatal

VSI_-4-RMSYSError

VSI_-5-RMSYSWarning

VSI_-3-RMCONNFatal

VSI_-4-RMCONNError

VSI_-3-RMTERMCONNFatal

VSI_-4-RMTERMCONNError

VSI_-5-RMTERMCONNWarni

VSI_-3-RMCONNAPIFatal

VSI_-4-RMCONNAPIError

VSI_-5-RMCONNAPIWarnin

VSI_-3-RMRSRCFatal

VSI_-4-RMRSRCError

VSI_-5-RMRSRCWarning

VSI_-3-RMBWCACFatal

VSI_-4-RMBWCACError

VSI_-5-RMBWCACWarning

VSI_-3-RMLCNREDFatal

VSI_-4-RMLCNREDError

VSI_-5-RMLCNREDWarning

VSI_-3-RMSCTFatal

VSI_-4-RMSCTError

VSI_-5-RMSCTWarning

VSI_-3-RMOAMFatal

VSI_-4-RMOAMError

VSI_-5-RMOAMWarning

VSI_-4-RM_ERROR

VSI_-7-RM_EVENT

DDTS : "pnst"

PNST-4-CREATE_EP_FAIL

PNST-4-IPC_FAIL

PNST-4-INVALID_MSG

PNST-4-WRITE_2_FIlE_FA

PNST-4-NULL_PTR

PNST-4-LOG_ERROR

PNST-5-LOG_WARNING

PNST-7-LOG_INFORMATIVE

DDTS "vsi"

VSIC-5-VSICGENERR

VSIC-5-VSICPROTERR

VSIC-5-VSICSYSERR

VSIC-5-VSICINTRNLERR

VSIC-2-VSIMAJORERR

VSIS-5-VSISERR

VSIS-5-SCTINVALIDVCERR

VSIS-5-SCTINVALIDSERVC

VSIS-4-DRIVERFAIL

VSIS-5-DALFAIL

VSIS-5-HWPROGFAIL

VSIS-4-SSIFAIL

VSIS-4-ADDVTOAMCONFAIL

VSIS-5-RAMSYNC

VSIS-5-GENERR

DDTS "vsi"

VSIC-5-VSICGENERR

VSIC-5-VSICPROTERR

VSIC-5-VSICSYSERR

VSIC-5-VSICINTRNLERR

VSIC-2-VSIMAJORERR

VSIS-5-VSISERR

VSIS-5-RAMSYNC

VSIS-5-GENERR

DDTS "system"

PMM-4-SWITCH_DEFAULT

PMM-4-SWCH_DEF_STR

PMM-4-SYNC_REQ_ERR

PMM-4-BUF_ERR

PMM-4-MSG_RSP_ERR

PMM-4-MSG_Q_ERR

PMM-5-PMM_TOUT

PMM-5-TMR_ERR

PMM-7-SWITCHOVER

PMM-7-IF_ERR

PMM-4-API_ERR

PMM-5-TASK_SPAWN_ERR

PMM-7-INIT_ERR

PMM-4-FSM_ERR

PMM-7-FSM_RPT

PMM-4-GO_ACTIVE_ERR

PMM-7-RST_REQ

PMM-4-DB_ERR

PMM-4-DNLD_ERR

PMM-4-RED_STATUS

PMM-7-BCAST_DATETIME

PMM-7-ENET_ENABLE

PMM-7-CLR_DB_REQ

PMM-7-NNAME_RCVD

DDTS "cema"

DDTS "unknown"

PNNI-5-PNNI_WARNING

PNNI-7-PNNI_INFORMATIV

DDTS "pnnisys"

PROO-2-InitErr

PROO-4-prootBadMsg

PROO-7-TaskSpawn

PROO-4-InternalError

PROO-4-SysError

PROO-4-soPRrcInitFail

PROO-6-soPRctcEvRcv

PROO-6-soPRsendEv

PROO-6-soPRsendAck

PROO-6-soPRsendNack

PROO-2-soPRipcAllocFai

PROO-2-soPRipcSendFail

PROO-4-soPRipcUnonOrg

PROO-4-soPRipcUnonEvt

PROO-4-ctcEventReg

PROO-4-ipcCount

PROO-7-soGoActiveEv

DDTS "pnnisys"

PROO-5-soPRstEvPend

PROO-5-soPRstInvEv

PROO-7-soPRstStart

PROO-7-soPRstStep

PROO-5-soPRerrFrom

PROO-4-soPRerrEv

PROO-5-soPRerrAck

PROO-4-soPRerrNack

PROO-7-soPRstProc

PROO-7-soPRrlbkStrt

PROO-6-soPRstDone

PROO-7-soPRstPost

PROO-7-soPRstRlbk

PROO-5-soPRrcErrSlot

PROO-6-soPRrcProc

PROO-6-soPRsmProc

PROO-2-soPRrcCdevReg

DDTS "pxm-diag"

PXMD-5-WARNING

DDTS : "pxm-diag"

PXM4-7-LOAD_SHARING_UN

PXM4-7-GEN_INFO

PXM4-7-TEST_FAILED

PXM4-4-PATH_CREAT_FAIL

PXM4-4-PATH_REMOVE_FAI

PXM4-4-XBAR_CNF_REQ_FA

PXM1-4-ERR

DDTS "driver"

DAL-2-DAL_INIT_ERR


LMI-5-GEN_ERR

SEVERITY: Warning
FORMAT: "%s, line %d %s error - %s, %d %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "General err lists err description, and optional arg list or identifier, followed by optional arg values."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

LMI-5-CTC_STATE_ERR

SEVERITY: Warning
FORMAT: "%s, line %d no transition from %d to %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "CTC err lists current CTC state and state trying to transition to."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: "Do a dsplog on the slot to retrieve event information."

DDTS "unknown"

LSM_-7-FBALLOC_FAIL

SEVERITY: Information
FORMAT: "ssiFrameBufferAlloc in %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Frame Buffer Allocation Error"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

LSM_-7-MSGSND_ERROR

SEVERITY: Information
FORMAT: "ssiMsgSend in %s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Message Send Error"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

LSM_-7-MSG_PROC_ERR

SEVERITY: Information
FORMAT: "msg processing error in %s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Message Proc Error"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

DDTS "snmp-ma"

MAST-7-INFO

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

MAST-7-MSG_INVALID

SEVERITY: Information
FORMAT: "%d: %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Master agent received an invalid message type"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MAST-7-CONNECT

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

MAST-4-RTM_CREATE_FAIL

SEVERITY: Error
FORMAT: "Failure Creating the RTM access semaphore."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Can not get/create RTM semaphore. This might prevent Master agent from initialize correctly."
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.

MAST-4-RTM_SEMTAKE_FAI

SEVERITY: Error
FORMAT: "RTM Update Semaphore failed to take."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Internal system 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.

MAST-4-RTM_SEMGIVE_FAI

SEVERITY: Error
FORMAT: "RTM Update Semaphore failed to give."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Internal system 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.

MAST-4-FAILED_INIT

SEVERITY: Error
FORMAT: "Failure initializing the Master Agent."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Internal system 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.

MAST-4-FAILED_CONFIG

SEVERITY: Error
FORMAT: "Failure Configuring the Master Agent."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Internal system 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.

MAST-4-FAILED_DBCREATE

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

MAST-4-FAILED_TBLCREAT

SEVERITY: Error
FORMAT: "Failure Creating DB Table, Error 0x%x."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Can not create table in the specified database with the disk db manager"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

MAST-4-FAILED_DBREGIST

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

MAST-4-FAILED_DBUPDATE

SEVERITY: Error
FORMAT: "Failure Updating database Table 0x%x."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Can not update database table on the disk."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. 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.

MAST-4-FAILED_DBREAD

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

MAST-4-FAILED_MALLOC

SEVERITY: Error
FORMAT: "%s_%d Failed to allocate memory."
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.
y engineering development.

MAST-4-FAILED_IPCMSG_A

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

MAST-4-SUBAGENT_NOTEXI

SEVERITY: Error
FORMAT: "%s_%d Subagent %d does not exist."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "The subagent might not exist or corrupted."
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.

MAST-4-OPEN_TRANSPORT

SEVERITY: Error
FORMAT: "%s_%d Open Transport Failed for %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Can not open IP transport."
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.

MAST-4-SENDTO_TRANSPOR

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

MAST-4-BIND_TRANSPORT

SEVERITY: Error
FORMAT: "%s_%d Bind Transport Failed for port %s."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Failed to bind to socket"
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.

MAST-4-FAILED_IPCSEND

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

MAST-4-FAILED_FUNCTION

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

MAST-4-EVENT_INVALID

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

MAST-4-IPCDATAPTR_INVA

SEVERITY: Error
FORMAT: "%s_%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.

MAST-6-T_CREATE

SEVERITY: Notice
FORMAT: "t_create failed in packets %lu, parse error %lu, get %lu, set %lu, get_next %lu, other %lu"
FLAG: No Flag
THROTTLING: Five Seconds
EXPLANATION: "SNMP master agent's queue is full. Too many requests"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MAST-6-METHOD

SEVERITY: Notice
FORMAT: "t_create method failed. Total set %lu, cleanup %lu, undo %lu, get %lu, test %lu, unknown %lu"
FLAG: No Flag
THROTTLING: Five Seconds
EXPLANATION: "SNMP Ev_Method_Request dropped by t_create()"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MAST-6-DISCARD

SEVERITY: Notice
FORMAT: "Discard timed out pdu total set - not started %lu started %lu, get - not started %lu started %lu"
FLAG: No Flag
THROTTLING: Five Seconds
EXPLANATION: "SNMP requests timeout and discarded"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MAST-6-BURST

SEVERITY: Notice
FORMAT: "%d pending %lu, dropped %lu, total %lu"
FLAG: No Flag
THROTTLING: Five Seconds
EXPLANATION: "SNMP requests flood/burst"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MAST-6-SA_REG_SEQ

SEVERITY: Notice
FORMAT: "%d %s slot %d chassis %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Subagent registration detected out of sequence"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MAST-6-SA_REG_MSG_LOST

SEVERITY: Notice
FORMAT: "%d %s count %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Subagent registration detected dis/connect message lost"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MAST-5-WARNING

SEVERITY: Warning
FORMAT: "Line %d %s"
FLAG: No Flag
THROTTLING: Five Seconds
EXPLANATION: "A generic warning message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MAST-4-SADISCONNECT

SEVERITY: Error
FORMAT: "Line %d Subagent %d at Slot %d is disconnected due to reason %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to receive Data from Subagents."
RECOMMENDED ACTION: "Collect information specified in field REQUIRED_INFO and call TAC."
REQUIRED INFO: "Collect information using following commands. dsplog -mod MASTER dsplog -mod SNMP dsplog -sl <slot number specified in the event>."

MAST-7-SAREGISTER

SEVERITY: Information
FORMAT: "Subagent %d Registered for Slot %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The subagent registered with master agent."
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.

MAST-7-SADEREGISTER

SEVERITY: Information
FORMAT: "%d Subagent %d De-Registered for Slot %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The subagent is deregistered with master agent."
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.
ment.

MAST-7-TBLOCKFAILED

SEVERITY: Information
FORMAT: "t_block failed for Subagent %d Request %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "SNMP operation is not success. This indicates that NO_SUCH_NAME is returned for GET request and GEN_ERROR for Set Request."
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.

MAST-4-CNFSNMP_ERRORMI

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.

MAST-4-CNFSNMP_IPCREPL

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

MAST-4-CNFSNMP_ERRORPA

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

MAST-4-FAILED_DBUPD_RE

SEVERITY: Error
FORMAT: "Failure Updating database table 0x%x"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Database update on the disk failed. Attempting to Restore previous values on disk"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. 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.

MAST-5-LARGE_TRAPSIZE

SEVERITY: Warning
FORMAT: "Trap Number %d with sequence number %d has size of %d that exceeds maximum limit %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Trap server received a trap which has size that exceeds the maximum limit. It was sent out but could not be stored in the RTM log completely"
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.

MAST-5-INVALID_PARAM

SEVERITY: Warning
FORMAT: "%d param %d caller 0x%x %s"
FLAG: No Flag
THROTTLING: Five Minutes
EXPLANATION: "An event to report invalid parameter"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "snmp-ma"

MIB-4-MEMALLOCFAILED

SEVERITY: Error
FORMAT: "%s Failed to allocate memory Line %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Memory Allocation failed. This is a resource issue and can potentially cause severe memory issues"
RECOMMENDED ACTION: "Please collect the info specified in REQUIRED_INFO and call TAC"
REQUIRED INFO: "Please collect the following
1. dsplog
2. dsperr
3. dspver
4. dspdate
5. ll for C, D, F
6. dspprfhist"

MIB-7-UNKNOWNFRONTMOD

SEVERITY: Information
FORMAT: "%s Unknown Front Card Type %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Could not get SNMP OID type for the Front Card"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-UNKNOWNLINEMODU

SEVERITY: Information
FORMAT: "%s Unknown Back Card Type %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Could not get SNMP OID type for the Back Card"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-NOENTPHYSINDEX

SEVERITY: Information
FORMAT: "%s entPhysicalIndex not found for Subclass %d Container %d Unit number %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "entPhysicalIndex entry not found in entPhysicalTable"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-NOENTITYFOUND

SEVERITY: Information
FORMAT: "%s No Entity found in the system"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "could not create entries in entPhysicalTable"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-INVALID_INDEX_E

SEVERITY: Information
FORMAT: "%s An invalid environmental monitoring index map tbl entry found"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-INVALID_THRESH_

SEVERITY: Information
FORMAT: "%s An invalid threshold index was detected"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-INVALID_ENTITY_

SEVERITY: Information
FORMAT: "%s An invalid entity table index was detected"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-MAX_THRESH_INDE

SEVERITY: Information
FORMAT: "%s Threshold index exceeded maximum allowed value"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-INDEX_ENTRY_EXC

SEVERITY: Information
FORMAT: "%s Index exceeded the environmental monitoring table limit"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-NULL_POINTER_FO

SEVERITY: Information
FORMAT: "%sLine #%d An illegal NULL pointer was identified"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-UNKNOWN_PHYSICA

SEVERITY: Information
FORMAT: "%s An unknown physical entity type was received"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-ENTITY_TABLE_AD

SEVERITY: Information
FORMAT: "%s An error was detected in adding an entry to the entity table"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-ENTITY_TABLE_UP

SEVERITY: Information
FORMAT: "%s An error was detected in updating an entry to the entity table"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-SHM_UPDATE_ERRO

SEVERITY: Information
FORMAT: "%s An error was detected in getting SHM environmental device info"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-INVALID_SHM_ENT

SEVERITY: Information
FORMAT: "%s An invalid number of ENVMON entries was received from the SHM"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-GET_SENSOR_THRE

SEVERITY: Information
FORMAT: "%s An error was detected in getting the next sensor threshold"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-INVALID_ENTITY_

SEVERITY: Information
FORMAT: "%s An invalid entity physical subclass was detected"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-ENTITY_TABLE_EX

SEVERITY: Information
FORMAT: "%s The maximum number of entity table entries was exceeded"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

MIB-7-UNEXPECTED_CONT

SEVERITY: Information
FORMAT: "%s An unexpected flow of control was detected"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "ccma"

OAM-4-OAMTIMERFAIL

SEVERITY: Error
FORMAT: "Could not start OAM timer"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Timer for polling VC Table didn't start"
RECOMMENDED ACTION: "This event is logged by OAM module while creation/restart of a timer for monitoring VC Table updates fails. Check the logs for getting more information. Note that this timer is started only for non-OC48 AXSM cards"
REQUIRED INFO: "From PXM card, collect :
1) dsprevs,
2) dsplog for that slot,
3) dsperr for that slot,

OAM-4-CPRONOTIFYFAIL

SEVERITY: Error
FORMAT: "%s: VPI = %d, VCI = %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "OAM notification to CPRO about change in connection alarm status failed. The alarm(s) may be in INGRESS or EGRESS or both directions"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: "From PXM card, collect :
1) dsprevs,
2) dsplog for that slot,
3) dsperr for that slot,
From AXSM card, collect :
1) dspports,
2) dspcon for that connection,
3) dsplns."

OAM-4-LOG

SEVERITY: Error
FORMAT: "OAM event %s %s, %ld, %ld, %ld\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

OAM-7-ERROR

SEVERITY: Information
FORMAT: "OAM error %s %s, %ld, %ld, %ld,\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "OAM Application Error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "pnnisys"

ATM-4-UNSUPPORTED_QOS

SEVERITY: Error
FORMAT: "ATM failed to create VC on Interface %s, (Cause of the failure Invalid traffic shaping parameters or out of rate queues."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Unsupported QoS Parameters"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "Interface namestring in the format string"

ATM-4-OUT_OF_VCDS

SEVERITY: Error
FORMAT: "ATM failed to create VC on Interface %s, (Cause of the failure All VCDS used.)"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Ran out of VCDs"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "Interface namestring in the format string"

ATM-5-UNMATCHUNIVERSI

SEVERITY: Warning
FORMAT: "(%d/%d/%d%d) %s. Please verify peer UNI version"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "UNI version is not matching"
RECOMMENDED ACTION: "Verify peer UNI versions"
REQUIRED INFO: "No required info"

ATM-5-MTUCALLMISMATCH

SEVERITY: Warning
FORMAT: "Call from \n ATM NSAP - %s\n has mismatched PDU size - forward size is %d\n - backward size is %d,\n int %s PDU size %s %s "
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "The calling or called party has a maximum transmission unit (MTU) size configured that is different from the MTU size on the current interface."
RECOMMENDED ACTION: "Either change the configured MTU size on the current interface to that of the caller's or called party's interface, or change the caller's or called party's interface to match the current interface."
REQUIRED INFO: "No additional info required"

ATM-4-FAILCREATEVC

SEVERITY: Error
FORMAT: "ATM failed to create VC(VCD=%d, VPI=%d, VCI=%d) on Interface %s, (Cause of the failure %s)"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Failed to create VC"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please collect the output of CLIs
a) General dspver, depcds, dsplog, dsperr, dspmempart
b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,
c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,
d) Congestion dsppnportcc, dspsvcparm,
e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

ATM-5-ILMIKEEPALIVEFA

SEVERITY: Warning
FORMAT: "ILMI(%s) Restarting ATM signalling and ILMI. Keepalive failure detected."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Adjacent peer device is not responding to ILMI Keepalive polling."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please collect the output of CLIs
a) General dspver, depcds, dsplog, dsperr, dspmempart
b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,
c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,
d) Congestion dsppnportcc, dspsvcparm,
e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

ATM-5-ILMICONFIGCHANG

SEVERITY: Warning
FORMAT: "ILMI(%s) Restarting ATM signalling and ILMI. Peer Configuration change detected."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Configuration of adjacent peer device has been changed."
RECOMMENDED ACTION: "Wait for the interface to restart itself."
REQUIRED INFO: "No additional info required"

ATM-5-VPIVCIRANGE

SEVERITY: Warning
FORMAT: "VPI/VCI range parameters are dis-joint on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "MinSvccVci > MaxVci, after negotiation with the peer through ILMI."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please collect the output of CLIs
a) General dspver, depcds, dsplog, dsperr, dspmempart
b) Interface dsppnports, dsppnport, dsppnportrsrc, dsppnportcac, dsppnportsig,
c) Connection dsppncons, dspcons, dspsigstats, dsppnctlvc,
d) Congestion dsppnportcc, dspsvcparm,
e) Topology dsppnni-reachable-addr, dsppnni-routing-policy, dsppnni-path, dsppnni-link.

ATM-6-ATMSOFTSTART

SEVERITY: Notice
FORMAT: "Restarting ATM signalling and ILMI on %s."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The command just entered causes ATM Soft Restart."
RECOMMENDED ACTION: "Stand by and let ATM Signalling and ILMI to restart."
REQUIRED INFO: "No additional info required"

ATM-7-ILMINOAUTOCFG

SEVERITY: Information
FORMAT: "ILMI(%s) Auto-configuration is disabled, current interface parameters will be used at next interface restart."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The command just entered causes auto-configuration to be disabled, the most recently entered interface parameters will be used at next interface restart."
RECOMMENDED ACTION: "Be aware of what parameteres have been configured."
REQUIRED INFO: "No additional info required"

ATM-7-ILMIAUTOCFGALRE

SEVERITY: Information
FORMAT: "ILMI(%s) Auto-configuration already enabled."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Atm auto-configuration has been enabled already. 'atm auto-configuration' command just entered is ignored."
RECOMMENDED ACTION: "No action required."
REQUIRED INFO: "No additional info required"

ATM-7-ILMINOAUTOCFGAL

SEVERITY: Information
FORMAT: "ILMI(%s) Auto configuration already disabled."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Atm auto-configuration has been enabled already. 'no atm auto-configuration' command just entered is ignored."
RECOMMENDED ACTION: "No action required."
REQUIRED INFO: "No additional info required"

ATM-6-ILMIADDREG

SEVERITY: Notice
FORMAT: "Address registration on %s is enabled. It will be initiated at next interface restart."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The command just entered enables atm address registration."
RECOMMENDED ACTION: "Shut/no shut on this interface if need to start address registration right away otherwise wait for next interface restart."
REQUIRED INFO: "No additional info required"

ATM-6-ILMIACCFILTER

SEVERITY: Notice
FORMAT: "New access filter setting will be applied to registration of new addresses on %s."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The command just entered sets up new ilmi access filter for address registration. It only affects new addresses to be registered. The addresses already registered will not be affected."
RECOMMENDED ACTION: "Shut/no shut on this interface to restart address registration if need to remove addresses already registered but not permitted by the new access filter."
REQUIRED INFO: "No additional info required"

ATM-6-ILMIDEFACCFILTE

SEVERITY: Notice
FORMAT: "New global default access filter setting will be applied to registration of new addresses on interfaces using global default access filter."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The command just entered sets up new global default access filter for addres registration. It only affects new addresses to be registered on interfaces using the global default. The addresses already registered will not be affected."
RECOMMENDED ACTION: "Shut/no shut on desired interfaces to restart address registration if need to remove addresses already registered but not permitted by the new global default access filter."
REQUIRED INFO: "No additional info required"

DDTS "atmsig"

ATMS-4-NOSVC

SEVERITY: Error
FORMAT: "no SVC, %s"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Invalid address 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 cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-NOCALLREF

SEVERITY: Error
FORMAT: "Cannot find a Callref value to allocate %s"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Error in allocating a new call reference value"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_SVC_INSE

SEVERITY: Error
FORMAT: "ATMSIG(%s %d,%d - %04d/%02d) SVC wavl ins failedsvc 0x%x"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Error in adding SVC control block to internal data structure"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_SVC_DELE

SEVERITY: Error
FORMAT: "ATMSIG(%s %d,%d - %04d/%02d) SVC wavl del failedsvc 0x%x"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Error in deleting SVC control block from internal data structure"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_PRTY_INS

SEVERITY: Error
FORMAT: "ATMSIG(%s %d,%d - %04d/%02d) avl prty ins failedsvc 0x%x party 0x%x"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Error in adding control block to internal data structure"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_PRTY_DEL

SEVERITY: Error
FORMAT: "ATMSIG(%s %d,%d - %04d/%02d) avl prty del failedsvc 0x%x party 0x%x"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Error in deleting control block from internal data structure"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_CUG_INSE

SEVERITY: Error
FORMAT: "ATMSIG(%s)"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Error in adding control block to internal data structure"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_CUG_DELE

SEVERITY: Error
FORMAT: "ATMSIG(%s)"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Error in deleting control block from internal data structure"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-6-FAILHALFLEGREM

SEVERITY: Notice
FORMAT: "halfLeg removal failed, %s"
FLAG: Stack Trace
THROTTLING: Five Seconds
EXPLANATION: "Error in freeing up data structure"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-FAILXCONN

SEVERITY: Error
FORMAT: "Xconnect failed, %s"
FLAG: Stack Trace
THROTTLING: Five Seconds
EXPLANATION: "Failed to establish connection"
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 the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-5-CONFIG_ERROR

SEVERITY: Warning
FORMAT: "Configuration Error %s %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Error in Control Vc configuration"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

DDTS "ipc"

IPC-3-NOMEM

SEVERITY: Minor Alert
FORMAT: "No memory available for %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "The IPC protocol subsystem could not obtain the memory it needed."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-5-CONSISTENCY

SEVERITY: Warning
FORMAT: "Message failed consistency check %s"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "An internal inconsistency was found in some IPC data structures."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-6-SLAVELOG

SEVERITY: Notice
FORMAT: "VIP-%s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed up to the Route Processor (RP) or Route Switch Processor (RSP) for display. This message appears only if the user has configured the service slavelog command."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-6-NODELFUNC

SEVERITY: Notice
FORMAT: "Delayed init function not available"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "The IPC application cannot be initialized because its initialization function does not appear in the IPC initialization function list."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-3-UNLOCK

SEVERITY: Minor Alert
FORMAT: "Unlock done on already unlocked element"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "An internal inconsistency was found in some IPC data structures."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-3-LOCK

SEVERITY: Minor Alert
FORMAT: "Lock done a deleted element"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "An internal inconsistency was found in some IPC data structures."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-3-CANT_SEND

SEVERITY: Minor Alert
FORMAT: "Cannot send IPC message %s"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "An error occurred in the IPC slave discovery mechanism. It might result in a malfunction in the operation of the IPC."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-3-NODISPATCH

SEVERITY: Minor Alert
FORMAT: "Message for %d.%d has no receive queue or dispatch routine"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "The IPC user failed to provide any means of handling the received message."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative along with the output of the show ipc ports command."
REQUIRED INFO: No Required Info

IPC-4-DELETED

SEVERITY: Error
FORMAT: "Attempt to delete an IPC message (%p) a second time"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "An internal inconsistency was found in some IPC data structures."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative along with the output of the show ipc status and show ipc queue commands."
REQUIRED INFO: No Required Info

IPC-3-ONINT

SEVERITY: Minor Alert
FORMAT: "Called from interrupt level %s"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "The IPC user attempted a prohibited call into IPC while IPC was running on the interrupt stack."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative along with the output of the show ipc status command."
REQUIRED INFO: No Required Info

IPC-4-NOBUFF

SEVERITY: Error
FORMAT: "The %s IPC message header cache has emptied"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "The given IPC message header cache has emptied"
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative along with the output of the show ipc status command."
REQUIRED INFO: No Required Info

IPC-4-GIANT

SEVERITY: Error
FORMAT: "Request for giant IPC packet denied. Request size = %d"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Someone requested a message that was too large for the IPC system"
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative along with the output of the show ipc status command."
REQUIRED INFO: No Required Info

IPC-6-NULL

SEVERITY: Notice
FORMAT: "%s %s=0x%x, seq = %x"
FLAG: Stack Trace
THROTTLING: Thirty Seconds
EXPLANATION: "IPC message has Null Seat/Port/Callback."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-6-INVALID

SEVERITY: Notice
FORMAT: "%s %s=0x%x"
FLAG: MSG_TRACEBACK
THROTTLING: MSGDEF_LIMIT_SLOW
EXPLANATION: "While processing an incoming message, IPC encountered invalid data in its internal data structures."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-6-NULLDELFUNC

SEVERITY: Notice
FORMAT: "Passed Null Delayed function to register"
FLAG: MSG_TRACEBACK
THROTTLING: MSGDEF_LIMIT_SLOW
EXPLANATION: "IPC cannot register application's NULL function in the IPC initialization function list."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-3-NO_ACK_HANDLER

SEVERITY: Minor Alert
FORMAT: "No handler for ACK with data."
FLAG: MSG_TRACEBACK
THROTTLING: One Second
EXPLANATION: "A preview function appended data to an ACK at the sender, but there is no corresponding ACK handler at the receiver."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-5-GET_PAK_MSG

SEVERITY: Warning
FORMAT: "Failed to get ipc message for size=%d"
FLAG: MSG_TRACEBACK
THROTTLING: One Second
EXPLANATION: "System unable to allocate ipc message of required size."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-6-QFULL

SEVERITY: Notice
FORMAT: "IPC Q is full."
FLAG: MSG_TRACEBACK
THROTTLING: MSGDEF_LIMIT_SLOW
EXPLANATION: "IPC queue is full."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-3-PRECLOSE

SEVERITY: Minor Alert
FORMAT: "IPC port pre-closure overflow : 0x%x : 0x%x"
FLAG: MSG_TRACEBACK
THROTTLING: One Second
EXPLANATION: "An application attempts to close an ipc port when there are messages pending in retransmit queue and ipc defer table overflows."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

IPC-4-INV_CALLBACK

SEVERITY: Error
FORMAT: "An invalid notify callback called. Details Src %x.%x, Dest %x.%x"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "An invalid notification call back routine is set to notify the result of ipc_message_send."
RECOMMENDED ACTION: "Copy the error message exactly as it appears on the console, and report it to your technical support representative."
REQUIRED INFO: No Required Info

DDTS "ipc"

WATC-4-NOEVENT

SEVERITY: Error
FORMAT: "Deadlock on watched event type %s."
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "An internal inconsistency was found when waiting for internal resource. This might be a temporary one. If it still presists, this needs to be analysed by the development team."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Capture the following and contact your technical support representative.
a) dspcds
b) dspcd
c) dsperr
d) dsplog
e) dspred
f) dir "ERPM"

SYS-4-MGDTIMER

SEVERITY: Error
FORMAT: "%s%s, timer = %p."
FLAG: Stack Trace
THROTTLING: Ten Seconds
EXPLANATION: "A software or hardware error occurred. This is an internal error while manupulating the internel resource Managed Timer. If it persists still, this needs to be analysed by the development team."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Capture the following and contact your technical support representative.
a) dspcds
b) dspcd
c) dsperr
d) dsplog
e) dspred
f) dir "ERPM"

SYS-4-TIMERNEG

SEVERITY: Error
FORMAT: "Cannot start timer (%p) with negative offset (%d)."
FLAG: Stack Trace
THROTTLING: Ten Seconds
EXPLANATION: "An internal software error occurred while setting or updating the timer value. This should never happen and if it happens, it proceed further with the default timeout value. If the error keeps happen, call the TAC representative."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Capture the following and contact your technical support representative.
a) dspcds
b) dspcd
c) dsperr
d) dsplog
e) dspred
f) dir "ERPM"

SYS-7-DELETE_IPC_SEAT

SEVERITY: Information
FORMAT: "Deleting the IPC Seat and Ports for %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This is an informational Log whenever IOS IPC removes the seat and corresponding ports for that seat"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

DDTS "atmsig"

UTIL-4-TREE

SEVERITY: Error
FORMAT: "Data structure error--%s"
FLAG: Stack Trace
THROTTLING: One Minute
EXPLANATION: "A software error occurred, resulting in a data structure inconsistency."
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 the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

DDTS "alarms"

NAM-5-INVALIDINPUT

SEVERITY: Warning
FORMAT: "The input to the function %s() was invalid."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A parameter value was invalid."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NAM-5-PARMOUTOFTRANGE

SEVERITY: Warning
FORMAT: "Parm %s is out of range. The range is between %d and %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The parameter value for the named parameter is out of range."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NAM-5-PARMINVALID

SEVERITY: Warning
FORMAT: "Function %s - Parm %s value '0x%x' is invalid."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The parameter value is invalid. Function, parameter name, and value in hex is included.."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

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

NAM-5-SYS_RESPONSE_ER

SEVERITY: Warning
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The task failed to come up because the task could not create or bind the EPID(IPC end point communication identifier) to the task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NAM-5-ALARM_HANDLING

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

NAM-5-ALARM_HANDLING_

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

NAM-5-QUEUEFULL

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

DDTS "atmsig"

NCDT-5-ADD_CLK_SRC_FAI

SEVERITY: Warning
FORMAT: "%s Addition of %s clock source failed with clock Id %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Addition of clock source failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-5-DEL_CLK_SRC_FAI

SEVERITY: Warning
FORMAT: "%s Deletion of %s clock source failed with clock Id %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Deletion of clock source failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-5-INVALIDFCNCALL

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

NCDP-4-NULLPTR

SEVERITY: Error
FORMAT: "%s Parm %s is invalid at position %d."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Software Error. The parameter value for the named parameter acquired in named function is NULL."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO: "Collect node info on PNNI controller using dspver, dspcds, dsplog, dsperr and dspmem."

NCDP-4-APINULLPTR

SEVERITY: Error
FORMAT: "%s Parm %s is invalid at position %d."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was NULL."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO: "Collect node info on PNNI controller using dspver,

NCDP-5-INVMSGTYPE

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

NCDP-5-INVALIDCASE

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

NCDP-5-RCNOTOK

SEVERITY: Warning
FORMAT: "%s We called %s, but it did not return OK, rc '0x%x'. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we called the given function name, however it returned the given return code."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO: No Required Info

NCDP-5-VALOUTOFRNG

SEVERITY: Warning
FORMAT: "%s %s, '0x%x', is greater than %s, '0x%x'."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "First value given is greater than NCDP's max value. The system was not updated accordingly."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-5-INVALIDCODEEXEC

SEVERITY: Warning
FORMAT: "%s We executed a portion of code that we should not have."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we exectued a portion of code that we should not have. A bug must have been introduced in the code."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-5-INVALIDCONF

SEVERITY: Warning
FORMAT: "%s Given slave configuration '0x%x' and Num Clocks '0x%x' is invalid."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we are asked to perform a configurationin, but the data is invalid to proecced. There is a bug in the NCDP system"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-5-UNABLETOREACHCL

SEVERITY: Warning
FORMAT: "%s Given CLI Session Id is invalid, cannot reach CLI."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "In the given function, we needed to print a message to CLI, but could not because the CLI Session Id is invalid. Someone forgot to set it or overwrote it."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-4-CLIBLOCKED

SEVERITY: Error
FORMAT: "%s This function was called when CLI was still blocked '0x%x'."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The given function was called when CLI was still blocked. This call should never have been made."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO: No Required Info

NCDP-4-MALLOCFAIL

SEVERITY: Error
FORMAT: "%s Failed to allocate memory of size'0x%x', memType'0x%x', Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we failed to allocate memory for the given amount and memory type."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO: "Collect node info on PNNI controller using dspver, dspcds, dspmempart"

NCDP-5-UNEXPECTEDCASE

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

NCDP-5-ERRORRC

SEVERITY: Warning
FORMAT: "%s: Received an ERROR RC when calling %s. RC = '0x%x'. Pos: %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "We called a given function which failed to perform our request. For the given reason. This is not an error. However, it warrants a warning and shouldn't happen, but it is recoverable."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-5-NAKRSP

SEVERITY: Warning
FORMAT: "%s Received a NAK response for a request made. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we received a NAK response for a request made earlier."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-5-INVALIDLOGICALI

SEVERITY: Warning
FORMAT: "%s Logical ID returned is a negative one. Pos %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "In the given function, we received an invalid logical ID. The given physical address must be invalid."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-5-TRAPIGNORED

SEVERITY: Warning
FORMAT: "%s The trap is ignored because NCDP is blocked by user."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "We were called in the given function, but NCDP is already busy with processing other requests."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-5-UNKNOWNSLAVE

SEVERITY: Warning
FORMAT: "%s VSIMW rejected request because slave is unknown='0x%x'. Pos%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "We were called in the given function, but VSIMW rejected the request because of an unknown slave."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDP-7-INFO_CLOCK

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

DDTS "atmsig"

NCDT-4-NOMEM_WARN

SEVERITY: Error
FORMAT: "%s Could not allocate memory for %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Could not allocate memory"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-5-NULLPTR

SEVERITY: Warning
FORMAT: "%s Encountered a null pointer for %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Encountered a null pointer"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-6-UNKNOWN_EVT

SEVERITY: Notice
FORMAT: "%s Encountered an unknown Event %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Encountered an unknown Event"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-IPC_SEND_FAIL

SEVERITY: Error
FORMAT: "%s IPC send failed on Epid %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Encountered an unknown Event"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-5-PORT_INVLD

SEVERITY: Warning
FORMAT: "%s Invalid NULL Port Passed for %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid Null Port Passed "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-ADDVC_FAIL

SEVERITY: Error
FORMAT: "%s Add Control VC failed for %s PORT %d VPI %d VCI %d "
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Add Control Vc failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-DELVC_FAIL

SEVERITY: Error
FORMAT: "%s Del Control VC failed for PORT %d VPI %d VCI %d "
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Add Control Vc failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-TX_RX_LCN_NOT_S

SEVERITY: Error
FORMAT: "%s TX and RX LCNs are not same TX LCN %d RX LCN %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Transmit and Recieve LCNs are not same"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-SLAVE_ID_NOTPXM

SEVERITY: Error
FORMAT: "%s Slave id is not PXM but is %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Slave ID is not that of PXM"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-TMINIT_FAIL

SEVERITY: Error
FORMAT: "%s Initialization of timer %s failed"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Initialization of timer failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-TMSTOP_FAIL

SEVERITY: Error
FORMAT: "%s Stopping of timer %s failed"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Stopping of timer failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-ADD_CLK_SRC_FAI

SEVERITY: Error
FORMAT: "%s Addition of %s clock source failed with clock Id %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Addition of clock source failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-DEL_CLK_SRC_FAI

SEVERITY: Error
FORMAT: "%s Deletion of %s clock source failed with clock Id %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Deletion of clock source failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-5-INVLD_CASE

SEVERITY: Warning
FORMAT: "%s An invalid case was encountered for %s with value %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "An invalid case was encountered"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-GENERAL_ERR_INF

SEVERITY: Error
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "To cover error events which can be recorded in a string"
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative"
REQUIRED INFO: No Required Info

NCDT-7-GENERAL_INFO

SEVERITY: Information
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "To cover general events which can be recorded in a string"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-INVALID_ARG

SEVERITY: Error
FORMAT: "%s Recieved an invalid message type which is %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Recieved and invalid message type"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-7-CLK_TRAP

SEVERITY: Information
FORMAT: " Recieved a clock trap with reason %d for logical interface %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Recieved a clock trap for a failed clock source"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-DISABLE_PORT

SEVERITY: Error
FORMAT: "NCDP being downed on port %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "NCDP being downed on port because we could not latch on to clock signal"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-5-PORT_MARK_DOWN

SEVERITY: Warning
FORMAT: "NCDP not being downed on port %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "NCDP not downed on port because port has oper state up and admin state up"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCDT-4-IPC_Q_CREATE_FA

SEVERITY: Error
FORMAT: " IPC Queue Creation failed for queueId %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: " IPC Queue Creation Failure"
RECOMMENDED ACTION: "No Action Required"
REQUIRED INFO: "Collect logs using the command dsplog -mod SSI"
ssi Failures"

NCDT-4-IPC_Q_ATTACH_FA

SEVERITY: Error
FORMAT: " IPC Queue Attach failed for queueId %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: " IPC Queue Attachment Failure"
RECOMMENDED ACTION: "No Action Required"
REQUIRED INFO: "Collect logs using the command dsplog -mod SSI"

NCDT-4-NBSM_NOT_SUPP_T

SEVERITY: Error
FORMAT: "Clock source not configured on %d because NBSM does not support 2 clks"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Clock source not configured because NBSM does not support 2 clks"
RECOMMENDED ACTION: "Configure the clock source on another SM. As this SM does not support 2 clock sources"
REQUIRED INFO: No Required Info

NCDT-4-FRSM_NOT_SUPP_C

SEVERITY: Error
FORMAT: "Clock source not configured on %d because FRSM does not support clks"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Clock source not configured because FRSM does not support clks"
RECOMMENDED ACTION: "Configure the clock source on another SM. As this SM does not support clock sources"
REQUIRED INFO: No Required Info

NCDT-4-CLK_SET_NAK

SEVERITY: Error
FORMAT: "Clock set request for %d Nak-d by %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Clock set request was Nak-d during resync"
RECOMMENDED ACTION: "Deconfigure the clock that was Nak-d"
REQUIRED INFO: "Before deconfiguring clk source capture dspclksrcs"

NCDT-4-CLK_UNSET_NAK

SEVERITY: Error
FORMAT: "Clock unset request for %d Nak-d by %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Clock unset request was Nak-d during resync"
RECOMMENDED ACTION: "Ensure that clock database is consistent. Check dspclksrcs and dspclockinfo"
REQUIRED INFO: "Check ncdp clock db and clock manager db (dspclksrcs, dspclockinfo)"

DDTS "ncdp"

NCPT-2-MALLOC_FAILURE

SEVERITY: Major Alert
FORMAT: "Could not allocate memory for %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Could not allocate memory"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-IPC_FAILURE

SEVERITY: Error
FORMAT: "Could not allocate IPC message for %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Could not allocate IPC message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-DATAPTR_FAILURE

SEVERITY: Error
FORMAT: "Data Pointer get failure for %s in MBLK ptr %p"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Data Pointer get failure"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-MSG_SEND_FAIL

SEVERITY: Error
FORMAT: "IPC send failed on Epid %s for Message %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "IPC Send Failure"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-LCN_BIND_FAIL

SEVERITY: Error
FORMAT: "LCN Bind Failed for interface %d lcn %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "LCN Bind Failure"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-LCN_UNBIND_FAIL

SEVERITY: Error
FORMAT: "LCN Unbind Failed for interface %d lcn %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "LCN Unbind Failure"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-LCN_BINDABLE_ER

SEVERITY: Error
FORMAT: "LCN Not Binable for interface %d lcn %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "LCN Unbindable "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-UNKNOWN_PDU

SEVERITY: Error
FORMAT: "Unknown PDU in interface %d of type %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Unknown PDU error "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-UNKNOWN_MSG_TYP

SEVERITY: Error
FORMAT: "Unknown Message Type of type %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Unknown Message error "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-EP_CREATE_ERR

SEVERITY: Error
FORMAT: "EP Create Failed for %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "EP Create Error "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-PORT_SEARCH_FAI

SEVERITY: Error
FORMAT: "Port Could not be found for %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Port Search Failed "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-4-PORT_INDEX_UNAV

SEVERITY: Error
FORMAT: "Port Index Unavailable for port %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Port Index Unavailable"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NCPT-5-LOG_WARNING

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

NCPT-7-LOG_INFORMATIVE

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Informative event to be logged"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "boot/shm"

BOOT-4-NULL_PTR

SEVERITY: Error
FORMAT: "Ethernet Driver Structure pointer NULL"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Device driver is not loaded properly!"
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

NILE-7-ECHKERR

SEVERITY: Information
FORMAT: "NILE4 ECC Single Bit Error Access Address 0x%01x%08x Syndrome %02x"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Nile4 Ecc Memory Error detected and corrected"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NILE-7-MCHKERR

SEVERITY: Information
FORMAT: "NILE4 ECC Multi Bit Error Access Address 0x%01x%08x Syndrome %02x"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Nile4 Ecc Irrecoverable Memory Error detected"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

NILE-7-WPERR

SEVERITY: Information
FORMAT: "NILE4 Write protect Error violation = %d, Cause = %d, Violating Address = 0x%x, TaskId = %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Nile4 Ecc Memory Error detected and corrected"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "ccma"

OAM-5-LOG

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

DDTS "unknown"

OAM-7-INIT_SUCCESS

SEVERITY: Information
FORMAT: "OAM Task Init Success"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "OAM Task Init Success."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

OAM-7-RCV_MSG_FAIL

SEVERITY: Information
FORMAT: "OAM Message Receive Failed"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Message receive failed."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

OAM-7-RCV_CELL_FAIL

SEVERITY: Information
FORMAT: "OAM Cell Receive from SAR Failed"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Failure in receiving a CELL"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

DDTS "pxm-connmgm"

PCEM-5-PCEMAERR

SEVERITY: Warning
FORMAT: "PCEMA Error %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The error could be one of the following Sync RAM DB Register failure IPC Message send failure Sync RAM event register"
RECOMMENDED ACTION: Copy the error message 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

PCEM-5-PCEMAERRCODE

SEVERITY: Warning
FORMAT: "PCEMA Error Module %s Function %d Code %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This event is not use for now. Please add in explanation if you must use this event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCEM-4-RAMSYNC

SEVERITY: Error
FORMAT: "%s, line %d Ram Sync %s error - errno = 0x%x, resetCause = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Ram sync related problems/errors"
RECOMMENDED ACTION: Copy the error message 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

PCEM-4-GENERR

SEVERITY: Error
FORMAT: "%s, line %d PCEMA %s error,errno %d "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "General System Level Errors"
RECOMMENDED ACTION: Copy the error message 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

PCEM-5-LSLOTINFOERR

SEVERITY: Warning
FORMAT: "Got LslotInfo error for slot %d in Function %s on line %d , errno = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Got error trying to access logical slot information "
RECOMMENDED ACTION: Copy the error message 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

PCEM-5-SLOTRESRVERR

SEVERITY: Warning
FORMAT: "Unable to reserve lslot %d due to errno %d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Got error trying to Reserve a slot "
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

DDTS "pxm-connmgm"

PCPR-4-PASSTHROREGFAIL

SEVERITY: Error
FORMAT: "Could not register for passthrough"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Could not register for passthrough for add/del controller."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

PCPR-5-INVALIDRATEVENT

SEVERITY: Warning
FORMAT: "Invalid rat event"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Invalid system event coming from parent process."
RECOMMENDED ACTION: Copy the error message 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

PCPR-2-SYNCRAMERR

SEVERITY: Major Alert
FORMAT: "%s Sync Ram Error at line %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "This error indicates a general error in sync ram area"
RECOMMENDED ACTION: Copy the error message 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

PCPR-5-PCPROTIMERFAIL

SEVERITY: Warning
FORMAT: "Could not start pcPro timer in function %s, line %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Could not start pcPro timer due to system service interface issue."
RECOMMENDED ACTION: No Recommended Action
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

PCPR-6-PCPROTIMERSET

SEVERITY: Notice
FORMAT: "Scheduled timeout in function %s, line %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Scheduled a timeout."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCPR-4-PCPROMSGHDLRFAI

SEVERITY: Error
FORMAT: "Error in attaching pcPro msg handler"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "This error indicates a message handler cannot be attached to the pcpro task. A system problem may have happened. Pcpro task will not be functional."
RECOMMENDED ACTION: Copy the error message 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

PCPR-4-PCPRONAMEBINDFA

SEVERITY: Error
FORMAT: "Error in binding name to the slot"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "This error indicates pcpro task cannot go to active state or standby state. A system problem may have happened. Pcpro task will not be functional."
RECOMMENDED ACTION: Copy the error message 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

PCPR-5-IFAUDITFAIL

SEVERITY: Warning
FORMAT: "Interface audit fails"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Interface audit fails"
RECOMMENDED ACTION: Copy the error message 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

PCPR-5-CONNAUDITFAIL

SEVERITY: Warning
FORMAT: "Connection audit on interface %d fails"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Connection audit on interface %d fails"
RECOMMENDED ACTION: Copy the error message 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

PCPR-5-CONNAUDITMISMAT

SEVERITY: Warning
FORMAT: "Found mismatched connection with lin = %d vpi = %d vci = %d lcn = %d during Audit\n"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Found mismatched connection during audit."
RECOMMENDED ACTION: Copy the error message 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

PCPR-4-COMEPCREATEFAIL

SEVERITY: Error
FORMAT: "Error creating communication endpoint"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "This error indicates a communication endpoint cannot be created for the pcpro task. Pcpro task will not be functional. A system problem may have happened."
RECOMMENDED ACTION: Copy the error message 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
Id>"

PCPR-4-TASKCREATEFAIL

SEVERITY: Error
FORMAT: "Error creating ram sync task"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "The ram sync task is used for syncing data to the standby PXM. This error indicates the ram sync task cannot be created. A system resource problem may have happened. This error will not affect the activities on the active PXM."
RECOMMENDED ACTION: Copy the error message 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

PCPR-4-TASKDELETEFAIL

SEVERITY: Error
FORMAT: "Error deleting ram sync task"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "The ram sync task is used for syncing data to the standby PXM. This error indicates the ram sync task cannot be deleted. A system problem may have happened. This error will not affect the activities on the active PXM."
RECOMMENDED ACTION: Copy the error message 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

PCPR-4-INVALID_CNTRLR_

SEVERITY: Error
FORMAT: "Error in retrieving controller information"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Error in retrieving controller information from shelf manager. There are two incidents of this error one is when system is booting up, which is not recoverable. The other one is from CLI command. Connections will not be provisioned."
RECOMMENDED ACTION: Copy the error message 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

PCPR-4-SYNCRAMINITFAIL

SEVERITY: Error
FORMAT: "Error registering with syncRam manager"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Error registering with syncRam manager. This error will not affect the activities on the active PXM. However, the standby PXM will not be functional."
RECOMMENDED ACTION: Copy the error message 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

PCPR-4-CONN_DEL_ERROR

SEVERITY: Error
FORMAT: "Connection delete error from controller"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Connection delete error from controller"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please capture the following information from the PXM45 cli and call your TAC support
1) dspcds/dspcd
2) dspver
3) dsplog -sl <slot which is experiencing the problem>
4) dsplog -sl < redundant slot if configured>
5) dsperr for the above slots.
6) Save the core file if required

PCPR-4-CONN_ADD_ERROR

SEVERITY: Error
FORMAT: "Connection addition failed in PXM-CM%s %d pcproSmDbFreeGet returned %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Connection addition failed in PXM-CM due to no free node"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PCPR-7-INVALID_CNTRLR_

SEVERITY: Information
FORMAT: "Invalid controller id "
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Invalid controller id"
RECOMMENDED ACTION: "Add a valid controller ID."
REQUIRED INFO: No Required Info

PCPR-4-RESERVED_CARDTY

SEVERITY: Error
FORMAT: "%s Unable to get reserved card type for slot %d "
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Unable to get reserved card type"
RECOMMENDED ACTION: No Recommended Action
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

PCPR-4-INVALIDSLOT_ERR

SEVERITY: Error
FORMAT: "Slot %d is either unreserved or reserved for unsupported card type, line %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Configuration exists for unreserved slot or slot that is reserved for unsupported card type"
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

PCPR-5-SEM_TIMEOUT

SEVERITY: Warning
FORMAT: "%s Semaphore timeout with error = %d "
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Slot based semaphore timeout while trying to access connection alarm database"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "shm"

REDM-2-pRedmanInitErr

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

REDM-2-pRedmanStdbySnd

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

REDM-1-pRedmanMallocEr

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

REDM-2-pRedmanInValidS

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

REDM-2-pRedmanInValidE

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

REDM-7-pRedmanInfo

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

REDM-7-pRedmanInfo1

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

REDM-7-pRedmanRootMsg

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

REDM-7-pRedmanTblReadE

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

REDM-7-pRedmanMap

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

REDM-2-pRedmanMapErr

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

REDM-7-pRedmanRecNo

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

REDM-7-pRedmanMaxRec

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

REDM-7-pRedmanitfDsp

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

REDM-2-pRedmanIfCbErr

SEVERITY: Major Alert
FORMAT: "%s, ifCb pointer null for given interface"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

REDM-2-pRedmanItfMapEr

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

REDM-2-pRedmanDiskErr

SEVERITY: Major Alert
FORMAT: "Error in Writing to Disk For %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "shm"

PCTC-7-PCTCINIT

SEVERITY: Information
FORMAT: "Initialization Failed."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Initialization Failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-PMMQUERY

SEVERITY: Information
FORMAT: "Query card info Failed."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Query card info Failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-MSGRECV

SEVERITY: Information
FORMAT: "Message receive Failed."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Message receive Failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-MSGSEND

SEVERITY: Information
FORMAT: "Message send failed, errno %x."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Message send failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-MSGHANDLE

SEVERITY: Information
FORMAT: "Message handler Failed with return code %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Message handler Failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-MSGTYPE

SEVERITY: Information
FORMAT: "Invalid message type %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Invalid message type"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-MSGDATA

SEVERITY: Information
FORMAT: "Invalid message data %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Invalid message data"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-CONVCGET

SEVERITY: Information
FORMAT: "pctcConVcGet Failed with return code %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "pctcConVcGet Failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-BADPCTCEPID

SEVERITY: Information
FORMAT: "Invalid pctc epid."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Invalid pctc Epid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-BADPMMEPID

SEVERITY: Information
FORMAT: "Invalid pmm epid."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Invalid pmm Epid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-RECVDATA

SEVERITY: Information
FORMAT: "Current state and event are %d, %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received message data"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-WRONGMSG

SEVERITY: Information
FORMAT: "Received wrong message from %d, type %d, data %d at state %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received wrong message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-STARTSPAWN

SEVERITY: Information
FORMAT: "Received card role %d and ready to spawn."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received card role and ready to spawn."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-PLATSPAWN

SEVERITY: Information
FORMAT: "Spawn platform task."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Spawn platform task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-PLATRAM

SEVERITY: Information
FORMAT: "Received platform task ram build start."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received platform task ram build start"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-PLATSYNC

SEVERITY: Information
FORMAT: "Received platform task ram build start."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received platform task db sync start"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-PLATREADY

SEVERITY: Information
FORMAT: "Received platform task ready."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received platform task ready"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-APPLSPAWN

SEVERITY: Information
FORMAT: "Spawn application task."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Spawn application task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-APPLRAM

SEVERITY: Information
FORMAT: "Received application task ram build start."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received application task ram build start"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-APPLSYNC

SEVERITY: Information
FORMAT: "Received application task ram build start."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received application task db sync start"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-APPLREADY

SEVERITY: Information
FORMAT: "Received application task ready."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received application task ready"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-WRONGSEQ

SEVERITY: Information
FORMAT: "Received wrong transition %d at %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received wrong transition sequency"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-WRONGSEQS

SEVERITY: Information
FORMAT: "Received wrong transition on standby %d at %d."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received wrong transition sequency on standby"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-7-APPLSPAWNFAIL

SEVERITY: Information
FORMAT: "Spawning of application %s failed."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Failed to spawn application."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

PCTC-4-EVENTFAIL

SEVERITY: Error
FORMAT: "Failed to send event %d to application %s."
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Failed to send event to application."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "cema"

PHY-4-PHY_ERR

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

PHY-5-FRM

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

DDTS "unknown"

PING-5-PING_WARNING

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

PING-7-PING_INFORMATIV

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

DDTS "ipc"

PIPC-4-MAJ_ERR_LOG

SEVERITY: Error
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "PIPC Severe 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. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Technical support representative.

PIPC-4-INV_PTR_RCVD

SEVERITY: Error
FORMAT: "Invalid pointer %s received.value %x"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Invalid pointer received by pipc from its message queue. This could cause the pxm not to process a pipc message from the SM."
RECOMMENDED ACTION: "Collect information specified in REQUIRED_INFO field"
REQUIRED INFO: "Collect a hot core dump. Collect event and error logs."

PIPC-4-INVALID_PTR

SEVERITY: Error
FORMAT: "Invalid pntr %s rcvd.value %x,srcAppl=%d,srcId=%d,msgFmt=%d,length=%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Invalid pointer received by pipc from its message queue. This could cause the pxm not to process a pipc message from the SM and thus cause syncing issues or clocking mismatches"
RECOMMENDED ACTION: "Collect information specified in REQUIRED_INFO field"
REQUIRED INFO: "Collect a hot core dump. Collect event and error logs."

DDTS "vsi"

VSIC-5-VSICGENERR

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

VSIC-5-VSICPROTERR

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

VSIC-5-VSICSYSERR

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

VSIC-5-VSICINTRNLERR

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

VSIC-2-VSIMAJORERR

SEVERITY: Major Alert
FORMAT: "%s, Vsi Major Alert %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "VSICORE Major Error Use dsperr to look at stack info"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSIS-5-INFO

SEVERITY: Warning
FORMAT: "%s, line %d %s, 0x%x, %d, %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSIS-5-VSISERR

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

VSIS-5-RAMSYNC

SEVERITY: Warning
FORMAT: "%s, line %d Ram Sync %s error - errno = 0x%x, resetCause = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSIS-5-GENERR

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

VSIS-5-SCTFAIL

SEVERITY: Warning
FORMAT: "%s, line %d Sct file failure %s error - errno = 0x%x, resetCause = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-VSIRMERR

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

VSI_-5-INFO

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

VSI_-3-RMCLKFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMCLKError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMCLKWarning

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMSYSFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMSYSError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMSYSWarning

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMCONNFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMCONNError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMTERMCONNFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMTERMCONNError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMTERMCONNWarni

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMCONNAPIFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMCONNAPIError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMCONNAPIWarnin

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMRSRCFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMRSRCError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMRSRCWarning

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMBWCACFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMBWCACError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMBWCACWarning

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMLCNREDFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMLCNREDError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMLCNREDWarning

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMSCTFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMSCTError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMSCTWarning

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-3-RMOAMFatal

SEVERITY: Minor Alert
FORMAT: "[FATAL 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RMOAMError

SEVERITY: Error
FORMAT: "[ERROR 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-5-RMOAMWarning

SEVERITY: Warning
FORMAT: "[WARNING 0x%04X %u] %s %u, %u, %u, %u, %u\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSI_-4-RM_ERROR

SEVERITY: Error
FORMAT: "RM ERROR: %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the RM application. It needs to be analyzed by TAC and possibly by the development team. In normal operation, such an error should never get reported."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative: "
REQUIRED INFO: " On PXM45:
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dsppnports.
7. dsppnportcac.
8. dsppnportrsrc.

VSI_-7-RM_EVENT

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

DDTS : "pnst"

PNST-4-CREATE_EP_FAIL

SEVERITY: Error
FORMAT: "can't creat Ep (msg q) %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "can't create EP for pnstat task (pnni stat task)"
RECOMMENDED ACTION: No action required
REQUIRED INFO: capture dsplog of PNST

PNST-4-IPC_FAIL

SEVERITY: Error
FORMAT: "can't get ipc %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "can't get ipc)"
RECOMMENDED ACTION: No action required
REQUIRED INFO: capture dsplog of PNST

PNST-4-INVALID_MSG

SEVERITY: Error
FORMAT: "invalid msg type: %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Invali meesage type"
RECOMMENDED ACTION: No action required
REQUIRED INFO: capture dsplog of PNST

PNST-4-WRITE_2_FIlE_FA

SEVERITY: Error
FORMAT: "%s %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Write to RAM fails "
RECOMMENDED ACTION: No action required
REQUIRED INFO: capture dsplog of SSI and PNST

PNST-4-NULL_PTR

SEVERITY: Error
FORMAT: "NULL PTR: %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "null pointer"
RECOMMENDED ACTION: No action required
REQUIRED INFO: capture dsplog of PNST

PNST-4-LOG_ERROR

SEVERITY: Error
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Error message to be logged"
RECOMMENDED ACTION: No action required
REQUIRED INFO: capture dsplog of PNST

PNST-5-LOG_WARNING

SEVERITY: Warning
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Warning message to be logged"
RECOMMENDED ACTION: No action required
REQUIRED INFO: capture dsplog of PNST

PNST-7-LOG_INFORMATIVE

SEVERITY: Information
FORMAT: "%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Informative event to be logged"
RECOMMENDED ACTION: No action required
REQUIRED INFO: capture dsplog of PNST

DDTS "vsi"

VSIC-5-VSICGENERR

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

VSIC-5-VSICPROTERR

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

VSIC-5-VSICSYSERR

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

VSIC-5-VSICINTRNLERR

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

VSIC-2-VSIMAJORERR

SEVERITY: Major Alert
FORMAT: "%s, Vsi Major Alert %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "VSICORE Major Error Use dsperr to look at stack info"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSIS-5-VSISERR

SEVERITY: Warning
FORMAT: "[VSI Warning, VSISERR, 0x%04X, %u] %s, %u, %u, %u, %u, %u, %u, %u, %u "
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Indicates a warning generated by the VSIS slave application. It needs to be analyzed by TAC and possibly by the development team. In normal operation, such a warning should not get reported. There may be times when this warning is reported due to temporary mismatch between the controller(PNNI) and the slave. This is only temporary and will get corrected."
RECOMMENDED ACTION: Please capture the following information and call your Cisco technical support representative.
REQUIRED INFO: On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dsppnports
7. dsppnportrsrc for pnports on the slot which had the error
8. dsppnportcac for pnports on the slot
9. dspconinfo
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspportsct gen <port #> for all ports on the slot
5. dsppart for each partition on the slot which had the error

VSIS-5-SCTINVALIDVCERR

SEVERITY: Warning
FORMAT: "[VSI Warning, SCTINVALIDVCERR, 0x%04X, %u]%s, %u"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "This error could be caused by invalid value in SCT file, possible reasons are
1. Invalid UPC_ENB value in SCT.
2. Invalid UPC_SELECT value in SCT."
RECOMMENDED ACTION: "On the specific card that reported this warning, issue CLI command dspsct gen <sctID> <egr|ing> [oc12|oc3|t3plpc|t3adm|e3|t1|e1] and check the UPC_ENB or UPC_SELECT BKT1_BKT2 information against the MIB to see if they are within defined ranges."
REQUIRED INFO: No Required Info

VSIS-5-SCTINVALIDSERVC

SEVERITY: Warning
FORMAT: "[VSI Warning, SCTINVALIDSERVCAT, 0x%04X, %u]%s, vsiServCat=%u"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "This error could be caused by invalid SERV-TYPE in SCT."
RECOMMENDED ACTION: "On the specific card that reported this warning, issue CLI command dspsct gen <sctID> <egr|ing> [oc12|oc3|t3plpc|t3adm|e3|t1|e1] and check the SERV-TYPE(DEC) information against the MIB to see if they are within defined ranges."
REQUIRED INFO: No Required Info

VSIS-4-DRIVERFAIL

SEVERITY: Error
FORMAT: "[VSI Error, DRIVERFAIL, 0x%04X, %u]%s, %u, %u, %u, %u, %u, %u, %u, %u."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error could be caused by device driver failure, the possible reasons are
1. Failure to add/delete/configure a connection in ATLAS.
2. Failure to add/delete/set an ELT CAM entry of xcvr type in the humvee.
3. Failure to configure/delete loopback in QE1210 or ATLAS.
4. Failure to program a connection in a SABRE."
RECOMMENDED ACTION: Please capture the following information and call your Cisco technical support representative.
REQUIRED INFO: On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dsppnports
7. dsppnportrsrc for pnports on the slot which had the error
8. dsppnportcac for pnports on the slot
9. dspconinfo
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspportsct gen <port #> for all ports on the slot
5. dsppart for each partition on the slot which had the error

VSIS-5-DALFAIL

SEVERITY: Warning
FORMAT: "[VSI Warning, DALFAIL, 0x%04X, %u]%s, sgNum=%u, %u"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error could be caused by DAL failure when trying to configure logical interfaces, possible reasons are
1. Failure to configure a SG (a.k.a VI) in a QE.
2. Failure to diable/enable a configured VI in a QE.
3. Failure to configure a CosB (a.k.a QBIN) in a QE."
RECOMMENDED ACTION: Please capture the following information and call your Cisco technical support representative.
REQUIRED INFO: On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dsppnports
7. dsppnportrsrc for pnports on the slot which had the error
8. dsppnportcac for pnports on the slot
9. dspconinfo
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspportsct gen <port #> for all ports on the slot
5. dsppart for each partition on the slot which had the error

VSIS-5-HWPROGFAIL

SEVERITY: Warning
FORMAT: "[VSI Warning, HWPROGFAIL, 0x%04X, %u]%s, sgNum=%u, %u"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error could be caused by failure to program hardware, the possible reasons are
1. Failure to program SG in HW.
2. Failure to set the SG state in HW.
3. Failure to configure COSBs on HW from SCT."
RECOMMENDED ACTION: Please capture the following information and call your Cisco technical support representative.
REQUIRED INFO: On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dsppnports
7. dsppnportrsrc for pnports on the slot which had the error
8. dsppnportcac for pnports on the slot
9. dspconinfo
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspportsct gen <port #> for all ports on the slot
5. dsppart for each partition on the slot which had the error

VSIS-4-SSIFAIL

SEVERITY: Error
FORMAT: "[VSI Error, SSIFAIL, 0x%04X, %u]%s, %u"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This is an internal software error, and is possibly caused by memory leak, memory corruption, or IPC failure."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

VSIS-4-ADDVTOAMCONFAIL

SEVERITY: Error
FORMAT: "[VSI Error, HWPROGFAIL, 0x%04X, %u]%s, sgNum=%u, vpi=%u, nniFlag=%u."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error could be caused by failure to add the VPC connection for the Virtual Trunk."
RECOMMENDED ACTION: Please capture the following information and call your Cisco technical support representative.
REQUIRED INFO: On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dsppnports
7. dsppnportrsrc for pnports on the slot which had the error
8. dsppnportcac for pnports on the slot
9. dspconinfo
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspportsct gen <port #> for all ports on the slot
5. dsppart for each partition on the slot which had the error

VSIS-5-RAMSYNC

SEVERITY: Warning
FORMAT: "%s, line %d Ram Sync %s error - errno = 0x%x, resetCause = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The error could cause by one of the following Sync RAM send failure IOV element add failure Send clock info failure IOV creation failure Cannot attach handler with communication endpoint"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSIS-5-GENERR

SEVERITY: Warning
FORMAT: "%s, line %d Vsi Slave %s error"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "IPC message failure related"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "vsi"

VSIC-5-VSICGENERR

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

VSIC-5-VSICPROTERR

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

VSIC-5-VSICSYSERR

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

VSIC-5-VSICINTRNLERR

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

VSIC-2-VSIMAJORERR

SEVERITY: Major Alert
FORMAT: "%s, Vsi Major Alert %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "VSICORE Major Error Use dsperr to look at stack info"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSIS-5-VSISERR

SEVERITY: Warning
FORMAT: "[VSI Warning, VSISERR, 0x%04X] %s, %u, %u, %u, %u"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Indicates a warning generated by the VSIS slave application. It needs to be analyzed by TAC and possibly by the development team. In normal operation, such a warning should not get reported. There may be times when this warning is reported due to temporary mismatch between the controller(PNNI) and the slave. This is only temporary and will get corrected."
RECOMMENDED ACTION: Please capture the following information and call your Cisco technical support representative.
REQUIRED INFO: On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dsppnports
7. dsppnportrsrc for pnports on the slot which had the error
8. dsppnportcac for pnports on the slot
9. dspconinfo
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspportsct gen <port #> for all ports on the slot
5. dsppart for each partition on the slot which had the error

VSIS-5-RAMSYNC

SEVERITY: Warning
FORMAT: "%s, line %d Ram Sync %s error - errno = 0x%x, resetCause = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The error could cause by one of the following Sync RAM send failure IOV element add failure Send clock info failure IOV creation failure Cannot attach handler with communication endpoint"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

VSIS-5-GENERR

SEVERITY: Warning
FORMAT: "%s, line %d Vsi Slave %s error"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "IPC message failure related"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "system"

PMM-4-SWITCH_DEFAULT

SEVERITY: Error
FORMAT: "Switch default %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The 'default' case in a switch statement has been hit."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-4-SWCH_DEF_STR

SEVERITY: Error
FORMAT: "Switch default %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The 'default' case in a switch statement has been hit."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-4-SYNC_REQ_ERR

SEVERITY: Error
FORMAT: "Sync request to %s with slot %d failed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Synchronization request between requested slots failed."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-4-BUF_ERR

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

PMM-4-MSG_RSP_ERR

SEVERITY: Error
FORMAT: "MSG resp err %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Message error happened during sending a response."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-4-MSG_Q_ERR

SEVERITY: Error
FORMAT: "MSG Q Err %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error happened in sending a 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. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-5-PMM_TOUT

SEVERITY: Warning
FORMAT: "PMM Timeout %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "PMM time out occurred"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-5-TMR_ERR

SEVERITY: Warning
FORMAT: "TimerError %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Application Timer Add function failed."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-7-SWITCHOVER

SEVERITY: Information
FORMAT: "Switchover %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Card assuming Mastership."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-7-IF_ERR

SEVERITY: Information
FORMAT: "Interface Error %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Input parameter to a function is invalid or a task reported error."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-4-API_ERR

SEVERITY: Error
FORMAT: "%s External API %s returns Error\n"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "API Error. This Error occurs when an API of a differnt module like SSI returns an 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. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "Provide Cisco Technical Support with the dsplog information of your system"

PMM-5-TASK_SPAWN_ERR

SEVERITY: Warning
FORMAT: "%s ssiTaskSpawn(\"%s\", %s) 0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Unable to create a new tak."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-7-INIT_ERR

SEVERITY: Information
FORMAT: "INIT Error %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Initialization Error"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-4-FSM_ERR

SEVERITY: Error
FORMAT: "FSM Error %s, cur=%s, prev=%s, evt=%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid state or received invalid event as an input parameter."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-7-FSM_RPT

SEVERITY: Information
FORMAT: "FSM Report %s, cur=%s, evt=%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A peer communication between the Master and the slave happend."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-4-GO_ACTIVE_ERR

SEVERITY: Error
FORMAT: "Go Active sync failed in module %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error occured while trying to go active."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-7-RST_REQ

SEVERITY: Information
FORMAT: "Reset request %s, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Resetting either Master or the Slave."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-4-DB_ERR

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

PMM-4-DNLD_ERR

SEVERITY: Error
FORMAT: "Standby Update Error %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Download or Ram update error occurred."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-4-RED_STATUS

SEVERITY: Error
FORMAT: "Redundancy Status Change for bit %s now %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Redundancy status changed."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

PMM-7-BCAST_DATETIME

SEVERITY: Information
FORMAT: "Periodic Broadcast of Date and Time to SMs and Standby PXM"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This information event indicates that the date and time is broadcast periodically to SMs and Standby PXM."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-7-ENET_ENABLE

SEVERITY: Information
FORMAT: "%s Enabling Ethernet Interface on ActivePXM in Slot %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This information event indicates that the Ethernet Interface on Active PXM is enabled."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-7-CLR_DB_REQ

SEVERITY: Information
FORMAT: "%s Clearing the Database due to new FW download and reset request from Master PXM"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This information event indicates that the Database is to be cleared on the Standby, whenever a new fw is Downloaded and reset request from Master PXM is issued."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

PMM-7-NNAME_RCVD