Table Of Contents

HSB-5-SSIMSGSENDFAIL

HSB-4-INCRUPDTFAIL

HSB-4-INCRUPDTDROP

HSB-4-DNLDBRAMFAIL

HSB-4-BRAMNOTFOUND

DDTS "drivers"

IFE-5-BADXFERSIZE

IFE-5-BADIFENUM

IFE-5-BADPORTNUM

IFE-5-BADHDRSIZE

IFE-5-BADCRC

IFE-5-INITAGAIN

IFE-5-ISRBEFOREINIT

IFE-5-FAILISR

IFE-5-BADADDRESS

IFE-5-BADECNTHRESH

IFE-5-BADDETHRESH

IFE-5-BADQEDEPTH

IFE-5-BADCIR

IFE-5-BADBcBe

IFE-5-IFE0RESET

IFE-5-IFE1RESET

DDTS "ilmi"

ILMI-4-SET_CNFG

ILMI-4-TIMER

ILMI-4-GEN_ERR

ILMI-5-GEN_WARNING

ILMI-7-GEN_INFO

ILMI-7-SYSUPTIMEWRAP

ILMI-7-CONNECTIVITYLOS

DDTS "unknown"

ILMI-4-INIT_ERROR_ILMI

ILMI-5-BAD_SNMP_VER

ILMI-5-ILMI_PARSE_ERR

ILMI-5-UNKNOWN_MSG

ILMI-4-RCV_MSG_ERROR

DDTS "ima"

IMA-6-MSG_GRP_VER_FAL

IMA-4-MODULE_ACTIVE

IMA-4-MODULE_INACTIVE

IMA-4-MODULE_SHUT

IMA-4-INVALID_DEV

IMA-4-DEVICE_SHUT

IMA-4-SEM_CREATE

IMA-4-REGTEST_FAIL

IMA-4-RAMTEST_FAIL

IMA-4-SRAMTEST_FAIL

IMA-4-DEVINIT_FAIL

IMA-4-INVALID_T1

IMA-4-INVALID_E1

IMA-4-INVALID_T3

IMA-4-LINE_UNAVAIL

IMA-4-INVALID_TC

IMA-4-UNSUPP_TC_MODE

IMA-4-INVALID_VPHYID

IMA-4-DD_CFG_TC

IMA-4-INVALID_GRP

IMA-4-TOOMANY_GRPS

IMA-4-UNSUPP_GRP_SYM

IMA-4-INVALID_IMA_ID

IMA-4-INVALID_P

IMA-4-INVALID_M

IMA-4-INVALID_IMA_LIN

IMA-4-INVALID_VER

IMA-4-INVALID_CLK_MOD

IMA-4-LNK_INVALID_DEV

IMA-4-UNSUPP_ALPHA

IMA-4-UNSUPP_BETA

IMA-4-UNSUPP_GAMMA

IMA-4-UNSUPP_DIFF_DEL

IMA-4-NO_LINK

IMA-4-NON_ZERO_LINKS

IMA-4-TOOMANY_LINKS

IMA-4-DUPLICATE_LINKS

IMA-4-TST_ACTIVE

IMA-4-TST_B4_2M

IMA-4-TST_NOT_ACTIVE

IMA-4-NULL_POINTER

IMA-4-PARAM_OUTOF_RAN

IMA-4-INVALID_TST_PTR

IMA-4-MSGQ_CREAT_FAIL

IMA-4-MSGQ_DEL_FAIL

IMA-4-TIMER_CREAT_FAI

IMA-4-TIMER_DEL_FAIL

IMA-4-MSG_RX

IMA-6-MSG_RX_TIMEOUT

IMA-4-MSG_SEND

IMA-4-TIMER_SET

IMA-4-TIMER_CANCEL

IMA-4-DD_INVALID_VAL

IMA-4-DD_ERROR

IMA-6-ICP_BUF_EMPTY

IMA-4-GHOST_GRP_EVT

IMA-4-GHOST_LNK_EVT

IMA-4-TRAP_SEND

IMA-6-RSTRT_ADJUST_DE

IMA-6-DELAY_INFO

IMA-6-REMOVE_DELAY_ON

IMA-4-FATAL

DDTS "shm"

INST-4-INSTALL_ERROR

INST-4-WRNG_EVT_RCVD

INST-4-GET_MSG_ERROR

INST-4-GET_BUFF_ERROR

INST-4-GET_EVENT_ERROR

INST-5-UNKNOWN_MSG

INST-4-RCV_MSG_FAILED

INST-5-INVALID_SLOT_NO

INST-7-SLOT_NO_SET

INST-7-GOT_SYNC_MSG

INST-7-TIMER_EXPIRED

INST-7-ACCESS_FILE_ERR

INST-4-MSGTO

INST-4-MSGNAK

INST-4-INVMSG

INST-4-RCVERR

INST-4-SENDERR

INST-7-RESET

INST-7-ABORT

INST-4-COPYERR

INST-7-COPY

INST-7-COPYDONE

INST-7-CHANGESTATE

INST-7-CHANGESTATETO

INST-7-COMMAND0

INST-7-COMMAND1

INST-7-COMMAND2

INST-7-COMMAND3

DDTS "ip-conn"

IP-4-IPCONN_ERR_EVT

IP-6-IPCONN_SPCL_EVT

IP-7-IPCONN_INFO_EVT

DDTS "iws"

IWS-5-INVALID_INIT_CA

IWS-5-API_CALL_WITHOU

IWS-5-NULL_PTR_ARGS

IWS-5-INVALID_CONFIGI

IWS-5-CONFIGINTERWORK

IWS-5-INVALID_CONFIGE

IWS-5-CONFIGEFCILOOKU

IWS-5-INVALID_CONFIGS

IWS-5-CONFIGSTATSUPDA

IWS-5-INVALID_CONFIGB

IWS-5-CONFIGBACKPRESS

IWS-5-INTERRUPT_INVOC

IWS-5-INVALID_INTERRU

IWS-5-INVALID_POS3_IN

IWS-5-INVALID_FRAMETR

IWS-5-INVALID_FRAMETR

IWS-5-INVALID_SELECT_

IWS-5-INVALID_CHAN_NU

IWS-5-INVALID_PORT_NU

IWS-5-INVALID_CHAN_ST

IWS-5-INNER_FUNCTION_

DDTS "pxm-connmgm"

LDRV-4-DBNUMLINEINVLD

LDRV-4-DBVERSIONINVLD

LDRV-4-PORTNUMINVLD

LDRV-4-UNKNOWNDCTYPE

LDRV-4-RCMPCONINVLD

LDRV-4-FPGADNLDERR

LDRV-4-BCDCMISMATCH

LDRV-4-LINEALARMCHG

LDRV-4-LINESTATALARM

LDRV-4-PLCPALARM

LDRV-4-PLCPSTATALARM

LDRV-7-CARDTYPEACTION

LDRV-4-UNKNOWNBCTYPE

LDRV-4-RCMPRSTFAIL

LDRV-5-MSGLENGTHINVLD

LDRV-5-CARDSTATEINVLD

LDRV-5-APPLTYPEINVLD

LDRV-5-MSGSRCIDINVLD

LDRV-5-MISDIRECTEDMSG

LDRV-4-RCVMSGFAILED

LDRV-4-MIBCNFMISMATCH

LDRV-4-SONETLINEINVLD

LDRV-4-SCRAMOPTINVLD

LDRV-4-SONETMEDINVLD

LDRV-4-SECTRACEINVLD

LDRV-4-ALMSERVINVLD

LDRV-4-DS3LNINVLD

LDRV-4-DS3REDSERV

LDRV-4-DS3LINEINVLD

LDRV-4-DBREGISTERERR

LDRV-4-DBTBLERROR

LDRV-4-DBTBLIDINVLD

LDRV-4-DBMISMATCH

LDRV-4-PLPPDS3LNINVLD

LDRV-4-PLPPOC3LNINVLD

LDRV-4-PLPPOC12LNINVLD

LDRV-4-CLKIMPINVLD

LDRV-4-CLKCONNINVLD

LDRV-4-CLKINBAND1INVLD

LDRV-4-CLKINBAND2INVLD

LDRV-4-CLKOPTINVLD

LDRV-4-CLKSRCUNKNOWN

LDRV-4-CLKMUXUNKNOWN

LDRV-4-CLKSRCCHANGE

LDRV-7-CLKSETREQ

LDRV-7-SETIFERR

LDRV-4-INVALID_PARMS

LDRV-6-QUNI_CFG_COND

DDTS "pxm-connmgm"

LDRV-3-DBNUMLINEINVLD

LDRV-3-DBVERSIONINVLD

LDRV-3-PORTNUMINVLD

LDRV-2-UNKNOWNDCTYPE

LDRV-2-RCMPCONINVLD

LDRV-2-FPGADNLDERR

LDRV-2-BCDCMISMATCH

LDRV-6-LINEALARMCHG

LDRV-6-LINESTATALARM

LDRV-6-PLCPALARM

LDRV-6-PLCPSTATALARM

LDRV-7-CARDTYPEACTION

LDRV-3-CARDUNKNOWNINS

LDRV-2-CARDREMOVED

LDRV-2-UNKNOWNBCTYPE

LDRV-2-RCMPRSTFAIL

LDRV-5-MSGLENGTHINVLD

LDRV-5-CARDSTATEINVLD

LDRV-5-APPLTYPEINVLD

LDRV-5-MSGSRCIDINVLD

LDRV-5-MISDIRECTEDMSG

LDRV-3-RCVMSGFAILED

LDRV-2-MIBCNFMISMATCH

LDRV-3-SONETLINEINVLD

LDRV-3-SCRAMOPTINVLD

LDRV-3-SONETMEDINVLD

LDRV-3-SECTRACEINVLD

LDRV-3-ALMSERVINVLD

LDRV-3-DS3LNINVLD

LDRV-3-DS3REDSERV

LDRV-3-DS3LINEINVLD

LDRV-3-DBREGISTERERR

LDRV-3-DBTBLERROR

LDRV-3-DBTBLIDINVLD

LDRV-3-DBMISMATCH

LDRV-2-PLPPDS3LNINVLD

LDRV-2-PLPPOC3LNINVLD

LDRV-2-PLPPOC12LNINVLD

LDRV-3-CLKIMPINVLD

LDRV-3-CLKCONNINVLD

LDRV-3-CLKINBAND1INVLD

LDRV-3-CLKINBAND2INVLD

LDRV-3-CLKOPTINVLD

LDRV-3-CLKSRCUNKNOWN

LDRV-3-CLKMUXUNKNOWN

LDRV-3-CLKSRCCHANGE

LDRV-7-CLKSETREQ

LDRV-7-SETIFERR

LDRV-5-IPCREATERR

LDRV-5-IPCNAMEBINDERR

LDRV-5-IPCHANDLERERR

LDRV-2-ADDLNERR

LDRV-2-LDRV10MSTASKSPA

LDRV-2-UPIFERR

LDRV-2-LMIALARMSETTRAP

LDRV-6-LMIALARMCLEARTR

LDRV-3-CTCTRANSFAIL

LDRV-5-INVALID_PARMS

LDRV-6-QUNI_CFG_CONDIT

LDRV-6-WRONG_US_REQ

LDRV-4-WRONG_RM_REQ

LDRV-4-WRONG_IN_REQ

LDRV-2-IN_FAILURE

LDRV-4-NON_UNI_REQ

LDRV-4-UN_EXPT_REQ

LDRV-4-PIPC

LDRV-4-UNEX_PIPC_MSG

LDRV-4-NULL_PIPC_MSG

LDRV-6-UNEX_CLI_CM

LDRV-6-APS_SWITCH

LDRV-6-APS_SWITCH2

LDRV-6-APS_SWITCH_FAIL

LDRV-3-APS_LINE_FAILUR

LDRV-3-APS_PLINE_FAILU

LDRV-6-APS_LINE_CLEAR

LDRV-6-APS_PLINE_CLEAR

LDRV-6-APS_USER_CLR

LDRV-6-APS_USER_LOCK

LDRV-6-LDRV_CD_EVT_ERR

LDRV-1-VC_CON_FAIL

LDRV-3-LDRV_DID_NOT_RU

DDTS "sys/uplink"

LMI-4-SWERROR

LMI-7-LMI_DEBUG_EVENT

LMI-7-FEEDER_EVENT

LMI-4-BAD_LMI_PORT

LMI-4-SEM_CREATE_ERR

LMI-4-BAD_LMI_IFNUM

LMI-5-BAD_IP_ADDR

LMI-4-BAD_FDR_CODE

LMI-4-BAD_MSG_REV

LMI-4-BAD_MEM_ALLOC

LMI-4-BAD_PTR

LMI-5-BAD_CASE_EVENT

LMI-4-GET_BULK_ERR

LMI-4-GET_RING_ERR

LMI-4-GET_SHELF_NM

LMI-5-GET_SHELF_IP

LMI-4-GET_SHELF_MOD_N

LMI-5-GET_SLOT_PORT

LMI-5-ADD_LMI_CHAN

LMI-5-DEL_LMI_CHAN

LMI-5-LMI_SIG_ERR

LMI-5-ABIT_CLR_ERR

LMI-4-MSG_SEND_ERR

LMI-4-MSG_ISEND_ERR

LMI-4-MSG_IPSEND_ERR

LMI-5-IMSG_ERR

LMI-4-SEM_GET_ERR

LMI-4-LCN_BIND_ERR

LMI-4-EP_CREATE_ERR

LMI-4-EP_NAME_BIND

LMI-5-EP_NAME_UNBIND

LMI-4-EP_HNDLR_BIND

LMI-5-EP_RESLV_ERR

LMI-5-GET_LSLOT_ERR

LMI-5-GET_PSLOT_ERR

LMI-4-STDBY_RDY_ERR

LMI-4-NO_PROVSN_ERR

LMI-4-ACTIVE_RDY_ERR

LMI-4-QUIESCENT_ERR

LMI-4-CTC_INIT_DONE_E

LMI-5-CTC_ACTV_RDY_ER

LMI-4-CTC_STDBY_RDY_E

LMI-5-BAD_STNDBY_MSG

LMI-5-BAD_LMI_STATE

LMI-4-BAD_DISK_IMAGE

LMI-5-INT_MSG_ERR

LMI-5-REGISTER_DB

LMI-5-MAX_NS_MSG_ERR

LMI-5-MAX_SPC_MSG_ERR

LMI-5-SPC_CNT_ERR

LMI-5-GET_IFC_ERR

LMI-4-TASK_SPAWN_ERR

LMI-4-DISKDB_REG_ERR

LMI-4-TIMEOUT_ERR

LMI-4-TIMER_CREATE_ER

LMI-4-EP_TIMEOUT_ERR

LMI-4-BAD_TASK_INDEX

LMI-5-IP_MSG_ERR

LMI-5-REGISTER_IFNUM

LMI-7-SYNCRAM_RESET

LMI-7-SYNCRAM_RESET_C

LMI-5-UNKNOWN_RAMDB

LMI-4-RCV_RDY_ERR

LMI-4-SYNC_DONE_ERR

LMI-5-LMI_DEBUG_ERR

LMI-4-LMI_BADSTATE_ER

LMI-4-LMI_BADCMD_ERR

LMI-4-LMI_BADRESP_ERR

DDTS "sys/uplink"

LMI-4-CPRO_GET_OP_STA

DDTS "feeder-lmi"

LMI-4-SWERROR

LMI-7-LMI_DEBUG_EVENT

LMI-4-BAD_LMI_PORT

LMI-4-SEM_CREATE_ERR

LMI-4-BAD_LMI_IFNUM

LMI-4-BAD_IP_ADDR

LMI-5-BAD_FDR_CODE

LMI-5-BAD_MSG_REV

LMI-4-BAD_MEM_ALLOC

LMI-4-BAD_PTR

LMI-5-BAD_CASE_EVENT

LMI-5-GET_BULK_ERR

LMI-4-GET_RING_ERR

LMI-4-GET_SHELF_NM

LMI-4-GET_SHELF_IP

LMI-4-GET_SHELF_MOD_N

LMI-4-ADD_LMI_CHAN

LMI-4-DEL_LMI_CHAN

LMI-4-LMI_SIG_ERR

LMI-5-ABIT_CLR_ERR

LMI-4-MSG_SEND_ERR

LMI-4-MSG_ISEND_ERR

LMI-4-MSG_IPSEND_ERR

LMI-4-IMSG_ERR

LMI-4-SEM_GET_ERR

LMI-4-LCN_BIND_ERR

LMI-4-EP_CREATE_ERR

LMI-4-EP_NAME_BIND

LMI-4-EP_NAME_UNBIND

LMI-4-EP_HNDLR_BIND

LMI-4-STDBY_RDY_ERR

LMI-4-NO_PROVSN_ERR

LMI-4-ACTIVE_RDY_ERR

LMI-4-QUIESCENT_ERR

LMI-4-CTC_INIT_DONE_E

LMI-4-CTC_ACTV_RDY_ER

LMI-4-CTC_STDBY_RDY_E

LMI-5-BAD_STNDBY_MSG

LMI-5-BAD_LMI_STATE

LMI-4-BAD_DISK_IMAGE

LMI-5-INT_MSG_ERR

LMI-5-MAX_NS_MSG_ERR

LMI-5-MAX_SPC_MSG_ERR

LMI-5-SPC_CNT_ERR

LMI-5-GET_IFC_ERR

LMI-4-TASK_SPAWN_ERR

LMI-4-DISKDB_REG_ERR

LMI-4-TIMEOUT_ERR

LMI-4-TIMER_CREATE_ER

LMI-4-EP_TIMEOUT_ERR

LMI-4-BAD_TASK_INDEX

LMI-4-REGISTER_IFNUM

LMI-7-SYNCRAM_RESET

LMI-7-SYNCRAM_RESET_C

LMI-5-UNKNOWN_RAMDB

LMI-4-RCV_RDY_ERR

LMI-4-SYNC_DONE_ERR

LMI-5-LMI_BADSTATE_ER

LMI-5-LMI_BADCMD_ERR

LMI-5-LMI_BADRESP_ERR

LMI-7-FEEDER_EVENT

LMI-5-INVALID_NS_LEN

LMI-2-LINK_FAILURE

LMI-7-LMI_LINK_OK

LMI-7-MAX_HASH_LIMIT_

LMI-7-INVALID_MSG_BUF

LMI-5-PERSIST_VSIERR

LMI-5-CTRLR_ERR

LMI-5-PERSIST_GENERR

LMI-4-OVERWRITE_EVENT

DDTS "sys/uplink"

LMI-4-EPID_ERR

LMI-5-SEM_ERR

LMI-5-SET_CNFG

HSB-5-SSIMSGSENDFAIL

SEVERITY: Warning

FORMAT: "%s() ssiMsgSendWait(slot %d, ptr 0x%x len %d) failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Sending of incremental update to Hot Standby failed."

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

REQUIRED INFO: No Required Info

HSB-4-INCRUPDTFAIL

SEVERITY: Error

FORMAT: "%s() hsbSendMessageToSm(slot %d, ptr 0x%x len %d) failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Forwarding of incremental update to Hot Standby 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: 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.

HSB-4-INCRUPDTDROP

SEVERITY: Error

FORMAT: "Increment Update from slot %d to %d mib id %d row %d dropped."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Incremental update dropped. Not in Hot Standby state yet."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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.

HSB-4-DNLDBRAMFAIL

SEVERITY: Error

FORMAT: "%s() downLoadBram(from %d, to %d) failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Downloading of the configuration to the card failed."

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

HSB-4-BRAMNOTFOUND

SEVERITY: Error

FORMAT: "%s() Could not find configuration file for slot %d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The configuration for the given slot was not found."

RECOMMENDED ACTION: "Make sure that the configuration file is present on the disk and the path is correctly specified. If the problem persists call your Cisco technical support representative and provide the representative with the gathered information."

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

DDTS "drivers"

IFE-5-BADXFERSIZE

SEVERITY: Warning

FORMAT: "APPI Xfer Size %d is unacceptable."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Cannot program Xfer size."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADIFENUM

SEVERITY: Warning

FORMAT: "IFE number %d is unacceptable."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed parameter check."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADPORTNUM

SEVERITY: Warning

FORMAT: "Port number %d is unacceptable."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed parameter check."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADHDRSIZE

SEVERITY: Warning

FORMAT: "Header size %d is unacceptable."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed parameter check."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADCRC

SEVERITY: Warning

FORMAT: "CRC %d is unacceptable."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed parameter check."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-INITAGAIN

SEVERITY: Warning

FORMAT: "%s() Driver already initialized."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "IFE driver getting initialized more than once."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-ISRBEFOREINIT

SEVERITY: Warning

FORMAT: "%s() ISR called before Init."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "IFE ISR called before ifeInit."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-FAILISR

SEVERITY: Warning

FORMAT: "%s() Fail to install ISR."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to install ISR."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADADDRESS

SEVERITY: Warning

FORMAT: "Bad pointer %p"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameter."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADECNTHRESH

SEVERITY: Warning

FORMAT: "Bad ECN Threshold %d in IFE per port Queues"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameter."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADDETHRESH

SEVERITY: Warning

FORMAT: "Bad DE Threshold %d in IFE per port Queues"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameter."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADQEDEPTH

SEVERITY: Warning

FORMAT: "Bad Q Depth %d in IFE per port Queues."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameter."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADCIR

SEVERITY: Warning

FORMAT: "Bad CIR %d in context database."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameter."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-BADBcBe

SEVERITY: Warning

FORMAT: "%d %d Both Bc and Be cannot be zero."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameter."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-IFE0RESET

SEVERITY: Warning

FORMAT: "Reset IFE%d, %d time(s), RxTxRatio = %f"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "IFE0 failed and being reset. Traffic maybe affected."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFE-5-IFE1RESET

SEVERITY: Warning

FORMAT: "Reset IFE%d, %d time(s), RxTxRatio = %f"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "IFE1 failed and being reset. Traffic maybe affected."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "ilmi"

ILMI-4-SET_CNFG

SEVERITY: Error

FORMAT: "%s, line %d Set Config Error %s - %d, %d, %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ILMI-4-TIMER

SEVERITY: Error

FORMAT: "%s, line %d Timer Error %s - %d, %d, %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ILMI-4-GEN_ERR

SEVERITY: Error

FORMAT: "%s, line %d %s error - %s, %d %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ILMI-5-GEN_WARNING

SEVERITY: Warning

FORMAT: "%s, line %d %s - %s, %d %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ILMI-7-GEN_INFO

SEVERITY: Information

FORMAT: "%s, line %d %s - %s, %d %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ILMI-7-SYSUPTIMEWRAP

SEVERITY: Information

FORMAT: "Sys up time wrap around happend for ifIndex = 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ILMI-7-CONNECTIVITYLOS

SEVERITY: Information

FORMAT: "connectivity loss for ifIndex = 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "unknown"

ILMI-4-INIT_ERROR_ILMI

SEVERITY: Error

FORMAT: "Init Error %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to create message queues during initialization."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

ILMI-5-BAD_SNMP_VER

SEVERITY: Warning

FORMAT: "ILMI_BAD_SNMP_VERSION %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Bad SNMP version."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

ILMI-5-ILMI_PARSE_ERR

SEVERITY: Warning

FORMAT: "ILMI_AUTH_PARSE_ERR %s "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SNMP community string parser error."

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

REQUIRED INFO: No Required Info

ILMI-5-UNKNOWN_MSG

SEVERITY: Warning

FORMAT: "UNknown message %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unknown message type received."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

ILMI-4-RCV_MSG_ERROR

SEVERITY: Error

FORMAT: "ILMI_RCV_MESSAGE_ERROR %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error in receiving 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. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.

REQUIRED INFO: No Required Info

DDTS "ima"

IMA-6-MSG_GRP_VER_FAL

SEVERITY: Notice

FORMAT: "IMA group %d NE version falls back to support FE's running version, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "IMA group NE version falls back to a lower supported version which FE group runs"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-MODULE_ACTIVE

SEVERITY: Error

FORMAT: "IMA SW module already active , at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "IMA software module is already initialized and active. This error is due to an attempted re-initialization"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-MODULE_INACTIVE

SEVERITY: Error

FORMAT: "IMA SW module is not active , at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "IMA software module is not active. It has to be initialized before any operation can be performed on it"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-MODULE_SHUT

SEVERITY: Error

FORMAT: "IMA software module could not be shut down, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "One of the stages in shutting down of the IMA module did not succeed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_DEV

SEVERITY: Error

FORMAT: "Mentioned IMA device (number = %d) is invalid, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Access to IMA device with invalid device number"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-DEVICE_SHUT

SEVERITY: Error

FORMAT: "IMA device (number = %d) shutdown failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Shutting down of an IMA device failed."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-SEM_CREATE

SEVERITY: Error

FORMAT: "Semaphore create failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Creation of SSI semaphore failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-REGTEST_FAIL

SEVERITY: Error

FORMAT: "Register diagnostics test failed on device %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Register diagnostic test failed on a device"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-RAMTEST_FAIL

SEVERITY: Error

FORMAT: "RAM diagnostics test failed on device %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Diagnostic test on a device RAM failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-SRAMTEST_FAIL

SEVERITY: Error

FORMAT: "SRAM diagnostics test failed on device %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "SRAM diagnostics test failed on device"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-DEVINIT_FAIL

SEVERITY: Error

FORMAT: "Addition/Initialization of device ( number = %d) failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Addition/Initialization of device failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_T1

SEVERITY: Error

FORMAT: "Invalid T1 line number %d, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "T1 line number is out of range"

RECOMMENDED ACTION: "Give a number within range"

REQUIRED INFO: No Required Info

IMA-4-INVALID_E1

SEVERITY: Error

FORMAT: "Invalid E1 line number %d, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "E1 line number is out of range"

RECOMMENDED ACTION: "Give a number within range"

REQUIRED INFO: No Required Info

IMA-4-INVALID_T3

SEVERITY: Error

FORMAT: "Invalid T3 line number %d, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "T3 line number out of range"

RECOMMENDED ACTION: "Give a number within range"

REQUIRED INFO: No Required Info

IMA-4-LINE_UNAVAIL

SEVERITY: Error

FORMAT: "Requested T1/T3 line %d is not available, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Requested T1/T3 line is already in use and not available"

RECOMMENDED ACTION: "Choose a line that is not already part of a group or TC"

REQUIRED INFO: No Required Info

IMA-4-INVALID_TC

SEVERITY: Error

FORMAT: "Invalid TC number %d, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "TC number is out of range or already in use or is not enabled"

RECOMMENDED ACTION: "Choose a valid TC number"

REQUIRED INFO: No Required Info

IMA-4-UNSUPP_TC_MODE

SEVERITY: Error

FORMAT: "TC mode %d not supported, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Requested TC mode is not supported. Only T1/T3 TC modes are supported"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_VPHYID

SEVERITY: Error

FORMAT: "Specified VPHY Id %d is not valid, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Virtual PHY id is not in range"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-DD_CFG_TC

SEVERITY: Error

FORMAT: "Configuration of TC number = %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Configuration of TC by the driver failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_GRP

SEVERITY: Error

FORMAT: "Invalid IMA group number %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Specified group number is either out of range, not active or already active"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TOOMANY_GRPS

SEVERITY: Error

FORMAT: "Limit of 42 groups in device %d is reached, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Cannot add more than 42 groups per device"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-UNSUPP_GRP_SYM

SEVERITY: Error

FORMAT: "Group symmetry mode %d not supported, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Only symmetrical configuration & operation mode is supported. Other modes are not supported"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_IMA_ID

SEVERITY: Error

FORMAT: "IMA ID %d specified is invalid, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Invalid IMA ID is specified"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_P

SEVERITY: Error

FORMAT: "Invalid min. number of links %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Invalid min. number of links (required to be active for the group to be operational)"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_M

SEVERITY: Error

FORMAT: "Unsupported value of M = %d, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Supported values are 128 for v1.0 & 32,64,128,256 for ver 1.1. Other values are invalid"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_IMA_LIN

SEVERITY: Error

FORMAT: "Specified link %d for group %d has problems,at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Specified link does not belong to group, or already is part of the group"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_VER

SEVERITY: Error

FORMAT: "Specified version %d is not supported, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Only version 1.0 & 1.1 are supported. Any other value is invalid"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_CLK_MOD

SEVERITY: Error

FORMAT: "Specified clock mode %d is invalid, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Only CTC & ITC are supported. Any other value is invalid"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-LNK_INVALID_DEV

SEVERITY: Error

FORMAT: "Specified link %d is not present in device %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Links added to a group should belong to the same device as the group"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-UNSUPP_ALPHA

SEVERITY: Error

FORMAT: "Specified value %d for alpha is not supported, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Only a default value of 2 is supported for alpha. Other values are invalid"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-UNSUPP_BETA

SEVERITY: Error

FORMAT: "Specified value %d for beta is not supported, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Only a default value of 2 is supported for beta. Other values are invalid"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-UNSUPP_GAMMA

SEVERITY: Error

FORMAT: "Specified value %d for gamma is not supported, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Only a default value of 1 is supported for gamma. Other values are invalid"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-UNSUPP_DIFF_DEL

SEVERITY: Error

FORMAT: "Link differrential delay %d is not supported, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "A maximum of 279 ms for T1 is supported"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-NO_LINK

SEVERITY: Error

FORMAT: "Group %d has no links, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "An operation was performed which required the group to have non-zero links"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-NON_ZERO_LINKS

SEVERITY: Error

FORMAT: "Group %d has non zero links, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "An operation was performed which required the group to have zero links. Before deleting a group, delete all links"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TOOMANY_LINKS

SEVERITY: Error

FORMAT: "Grp %d already has max. number of links, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "An IMA group can have a max of 12 links"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-DUPLICATE_LINKS

SEVERITY: Error

FORMAT: "Grp %d has duplicate set of links, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Only unique set of links can exist in a group"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TST_ACTIVE

SEVERITY: Error

FORMAT: "A connectivity test is already active on group %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Only one connectivity test can be performed on a group and only on one group at any time"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TST_B4_2M

SEVERITY: Error

FORMAT: "Attempted change in connectivity test on group %d before 2*M cell times, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "A connectivity test must be on for atleast 2*M cell times before it can be stopped or the pattern changed. This 2*M cell times roughly corresponds to 150 ms"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TST_NOT_ACTIVE

SEVERITY: Error

FORMAT: "connectivity test on group %d not active, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "No connectivity test running on a group"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-NULL_POINTER

SEVERITY: Error

FORMAT: "null pointer detected at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Range check error"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-PARAM_OUTOF_RAN

SEVERITY: Error

FORMAT: "Function input paramater value %d out of range, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Range check error"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-INVALID_TST_PTR

SEVERITY: Error

FORMAT: "Invalid connectivity test pattern %d in group %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Connectivity test pattern can be within [-1...255]."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-MSGQ_CREAT_FAIL

SEVERITY: Error

FORMAT: "SSI message queue creation failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SSI message queue creation failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-MSGQ_DEL_FAIL

SEVERITY: Error

FORMAT: "SSI message queue deletion failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SSI message queue deletion failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TIMER_CREAT_FAI

SEVERITY: Error

FORMAT: "SSI timer creation failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SSI timer creation failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TIMER_DEL_FAIL

SEVERITY: Error

FORMAT: "SSI timer deletion failed, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "SSI timer deletion failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-MSG_RX

SEVERITY: Error

FORMAT: "SSI message queue receive failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SSI message queue receive failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-6-MSG_RX_TIMEOUT

SEVERITY: Notice

FORMAT: "SSI message queue receive timed out, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Message queue receive times out when there are no pending messages"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-MSG_SEND

SEVERITY: Error

FORMAT: "SSI message queue send failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SSI message queue send failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TIMER_SET

SEVERITY: Error

FORMAT: "SSI timer %s set failed, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "SSI timer set failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TIMER_CANCEL

SEVERITY: Error

FORMAT: "SSI timer %s CANCEL failed, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "SSI timer CANCEL failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-DD_INVALID_VAL

SEVERITY: Error

FORMAT: "Invalid value %d read for device driver variable %s, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Invalid value read for a device driver variable"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-DD_ERROR

SEVERITY: Error

FORMAT: "device driver api returned error %d, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "device driver api returned error"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-6-ICP_BUF_EMPTY

SEVERITY: Notice

FORMAT: "ICP trace buffer is empty, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ICP trace buffer is empty"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-GHOST_GRP_EVT

SEVERITY: Error

FORMAT: "Event from a non existent group %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Event from a non existent group"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-GHOST_LNK_EVT

SEVERITY: Error

FORMAT: "Event from a non existent link %d, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Event from a non existent link"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-TRAP_SEND

SEVERITY: Error

FORMAT: "Failed to send trap %s, at line %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Failure in sending trap"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-6-RSTRT_ADJUST_DE

SEVERITY: Notice

FORMAT: "Cannot restart/adjust delay group %d at line %d during adjust delay/restart"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "A group cannot be restarted when a delay adjustment is going on in the group. The group cannot be configured either (exception GTSM integration time ) because configuring involves restarting the group. Similarly delay cannot be adjusted when group is going through startup. The 2 are mutually exclusive"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-6-DELAY_INFO

SEVERITY: Notice

FORMAT: "Could not get delay information for group %d at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "If none of the links in the group is good ( free of defects, LOS,LCD,LIF), then the delay information cannot be determined"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-6-REMOVE_DELAY_ON

SEVERITY: Notice

FORMAT: "Currently delay is being removed from ima group %d at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "When a grp remove delay operation is going on, any group or link set operation from SNMP or CLI is not allowed. The user must wait until the remove delay operation completes before reissuing the set command"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IMA-4-FATAL

SEVERITY: Error

FORMAT: "One or more of group,module, interrupt initializations failed, at line %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "One or more of group,module, interrupt initializations failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "shm"

INST-4-INSTALL_ERROR

SEVERITY: Error

FORMAT: "Init Error %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Initialization error in upgrade task."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

INST-4-WRNG_EVT_RCVD

SEVERITY: Error

FORMAT: " %s , CurrentEvent = %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Wrong event received."

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

REQUIRED INFO: No Required Info

INST-4-GET_MSG_ERROR

SEVERITY: Error

FORMAT: "Get Message %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Error in receiving messages."

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

REQUIRED INFO: No Required Info

INST-4-GET_BUFF_ERROR

SEVERITY: Error

FORMAT: " Get pipcGetBuffer Error %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Error in allocating a buffer."

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

REQUIRED INFO: No Required Info

INST-4-GET_EVENT_ERROR

SEVERITY: Error

FORMAT: "Get Event %s, %d "

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Bad event received."

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

REQUIRED INFO: No Required Info

INST-5-UNKNOWN_MSG

SEVERITY: Warning

FORMAT: "UNknown message %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unknown message type received."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-4-RCV_MSG_FAILED

SEVERITY: Error

FORMAT: "Init Error %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Error in receiving 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. 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

INST-5-INVALID_SLOT_NO

SEVERITY: Warning

FORMAT: "Invalid Slot Number, %s, %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "This function received an invalid input parameter."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-SLOT_NO_SET

SEVERITY: Information

FORMAT: "updateSlotNum Old S.N.= %d New S.N.=%d "

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Successful slot number update."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-GOT_SYNC_MSG

SEVERITY: Information

FORMAT: "Got Sync Msg from INSTALL ,Msg Q Id = %d "

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Received a sync message from INSTALL."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-TIMER_EXPIRED

SEVERITY: Information

FORMAT: " Timer Expired = %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Timer expired notification."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-ACCESS_FILE_ERR

SEVERITY: Information

FORMAT: "%s File Access Error for Upgrade/Downgrade"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "File read or write error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-4-MSGTO

SEVERITY: Error

FORMAT: "%s timeout waiting for response"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Timout waiting for 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. 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

INST-4-MSGNAK

SEVERITY: Error

FORMAT: "%s negative ack received"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "NAK message received notification."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

INST-4-INVMSG

SEVERITY: Error

FORMAT: "%s invalid message type %d"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Invalid card message."

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

REQUIRED INFO: No Required Info

INST-4-RCVERR

SEVERITY: Error

FORMAT: "%s error returned by ssiMsgReceive %d"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Error in receiving a CLI message."

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

REQUIRED INFO: No Required Info

INST-4-SENDERR

SEVERITY: Error

FORMAT: "%s error returned by ssiMsgSend %d"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Error in sending a CLI message."

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

REQUIRED INFO: No Required Info

INST-7-RESET

SEVERITY: Information

FORMAT: "%s card reset by the upgrade task reason %d"

FLAG: Stack Trace | Write to Bram

THROTTLING: One Second

EXPLANATION: "Other PXM has successfully been reset."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-ABORT

SEVERITY: Information

FORMAT: "%s aborting process (current state %d)"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Starting the abort of all the processes."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-4-COPYERR

SEVERITY: Error

FORMAT: "%s error copying %s to other PXM (%d)"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Downloading FW to a card failed."

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

REQUIRED INFO: No Required Info

INST-7-COPY

SEVERITY: Information

FORMAT: "%s copying %s to other PXM"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Downloading Firmware notification."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-COPYDONE

SEVERITY: Information

FORMAT: "%s copying %s to other PXM done"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Downloading of Firmware is successful."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-CHANGESTATE

SEVERITY: Information

FORMAT: "%s changing state from %d to %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Change of state nofication."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-CHANGESTATETO

SEVERITY: Information

FORMAT: "%s changing state to %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Change of sate nofication."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-COMMAND0

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "rstupgrade command notification."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-COMMAND1

SEVERITY: Information

FORMAT: "%s %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Beginning of install."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-COMMAND2

SEVERITY: Information

FORMAT: "%s %s %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Notification of setting primary/seconday PXM image."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

INST-7-COMMAND3

SEVERITY: Information

FORMAT: "%s %s %s %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "install command notification."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

DDTS "ip-conn"

IP-4-IPCONN_ERR_EVT

SEVERITY: Error

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event indicates an error condition in the IP Connectivity task. While important not all events indicate a critical 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: " a) dsplog -mod IPCONN on PXM

b) dspipif on PXM

c) dspsvcif on PXM

d) dsppvcif on PXM

e) dspipifcache on PXM

f) dspipconntask on PXM

g) If using SVC dsppnsysaddr on PXM dsppnports on PXM "

IP-6-IPCONN_SPCL_EVT

SEVERITY: Notice

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event indicates a change in IP Connectivity configuration. This is not an error condition."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

IP-7-IPCONN_INFO_EVT

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event represents debug information about the IP Connectivity task. Debug events can be enabled/disabled using the setipconndebug cli command. "

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

DDTS "iws"

IWS-5-INVALID_INIT_CA

SEVERITY: Warning

FORMAT: "IWS Error INVALID_INIT_CALL Code=(%u) #InitCalls=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-API_CALL_WITHOU

SEVERITY: Warning

FORMAT: "IWS Error API_CALL_WITHOUT_INIT Code=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-NULL_PTR_ARGS

SEVERITY: Warning

FORMAT: "IWS Error NULL_PTR_ARGS Code=(%u) Ptr=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_CONFIGI

SEVERITY: Warning

FORMAT: "IWS Error INVALID_CONFIGINTERWORKING Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-CONFIGINTERWORK

SEVERITY: Warning

FORMAT: "IWS Error INVALID_CONFIGINTERWORKING Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_CONFIGE

SEVERITY: Warning

FORMAT: "IWS Error INVALID_CONFIGEFCILOOKUP Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-CONFIGEFCILOOKU

SEVERITY: Warning

FORMAT: "IWS Error CONFIGEFCILOOKUP_FAIL Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_CONFIGS

SEVERITY: Warning

FORMAT: "IWS Error INVALID_CONFIGSTATSUPDATES Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-CONFIGSTATSUPDA

SEVERITY: Warning

FORMAT: "IWS Error CONFIGSTATSUPDATES_FAIL Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_CONFIGB

SEVERITY: Warning

FORMAT: "IWS Error INVALID_CONFIGBACKPRESSURE_THRESHOLD Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-CONFIGBACKPRESS

SEVERITY: Warning

FORMAT: "IWS Error CONFIGBACKPRESSURE_THRESHOLD_FAIL Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INTERRUPT_INVOC

SEVERITY: Warning

FORMAT: "IWS Error INTERRUPT_INVOCATION Reg=(0x%08x)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_INTERRU

SEVERITY: Warning

FORMAT: "IWS Error INVALID_INTERRUPT_TYPE Code=(%u) INVALID_INTERRUPT_TYPE=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_POS3_IN

SEVERITY: Warning

FORMAT: "IWS Error INVALID_POS3_INTERFACE_NUM Code=(%u) interfaceNum=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_FRAMETR

SEVERITY: Warning

FORMAT: "IWS Error INVALID_FRAMETRACECONTROL Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_FRAMETR

SEVERITY: Warning

FORMAT: "IWS Error INVALID_FRAMETRACENUMBER Code=(%u) ConfigVal=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_SELECT_

SEVERITY: Warning

FORMAT: "IWS Error INVALID_SELECT_DECODE Code=(%u) selectDecode=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_CHAN_NU

SEVERITY: Warning

FORMAT: "IWS Error INVALID_CHAN_NUM_ARG Code=(%u) Chan=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_PORT_NU

SEVERITY: Warning

FORMAT: "IWS Error INVALID_PORT_NUM_ARG Code=(%u) Port=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INVALID_CHAN_ST

SEVERITY: Warning

FORMAT: "IWS Error INVALID_CHAN_STATS_RANGE Code=(%u) ChanBeg=(%u) nChans=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IWS-5-INNER_FUNCTION_

SEVERITY: Warning

FORMAT: "IWS Error INNER_FUNCTION_FAILED Code=(%u)\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "pxm-connmgm"

LDRV-4-DBNUMLINEINVLD

SEVERITY: Error

FORMAT: "Function= %s Line number %d..%d exceeded Max %d Line per PSM"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Config update function detected number of requested lines exceed the maximum number of line in the PSM."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-DBVERSIONINVLD

SEVERITY: Error

FORMAT: "Invalid Database version detected for %s, from%d.%d to%d.%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to update the configuration data base because of the invalid DB version number."

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

REQUIRED INFO: No Required Info

LDRV-4-PORTNUMINVLD

SEVERITY: Error

FORMAT: "%sInvalid Port number %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Requested function detected invalid Port number passed."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-UNKNOWNDCTYPE

SEVERITY: Error

FORMAT: "In function %s Unknown Daughter card type %d is detected "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The pio does not indicate a known daugter card type."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-RCMPCONINVLD

SEVERITY: Error

FORMAT: "Invalid RCMP connection size %d for the DC card = %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The DC identification bits are invalid for number of RCMP 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: No Required Info

LDRV-4-FPGADNLDERR

SEVERITY: Error

FORMAT: "Fpga download on card ID = %d failed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "System routine to download FPGA image on a card returns fail."

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

REQUIRED INFO: No Required Info

LDRV-4-BCDCMISMATCH

SEVERITY: Error

FORMAT: "Back Card and Daughter card types don't match BC=%d, DC=%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Back card and daughter card type are mismatched."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-LINEALARMCHG

SEVERITY: Error

FORMAT: "Line Alarm on , port = %d, severity = %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Line alarm has been switched to a new state. The severity can be Major, Minor or Clear."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-LINESTATALARM

SEVERITY: Error

FORMAT: "Statistical Alarm on Port %d, severity =%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Statistical alarm has been switched to a new state. The severity can be Major, Minor or Clear."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-PLCPALARM

SEVERITY: Error

FORMAT: "Plcp Alarm on Port %d, severity =%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Plcp alarm has been switched to a new state. The severity can be Major, Minor or Clear."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-PLCPSTATALARM

SEVERITY: Error

FORMAT: "Plcp Statistical Alarm on Port %d, severity =%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Plcp alarm has been switched to a new state. The severity can be Major, Minor or Clear."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-7-CARDTYPEACTION

SEVERITY: Information

FORMAT: "%s of type %s , %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Back card or Daughter card inserted or removed Line Driver enters Fail state if BC or DC is removed Line Driver enters Standby state if bot BC and DC are inserted and matched."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

LDRV-4-UNKNOWNBCTYPE

SEVERITY: Error

FORMAT: "Unknown Backcard card %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " The novram read from the card does not have a valid backcard type The line Driver enters Fail state until a valid back card is Inserted."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-RCMPRSTFAIL

SEVERITY: Error

FORMAT: "RCMP reset Failed for DC type %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "RCMP reset fail for the specified Daughter card. Line Driver enters Fail state."

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

REQUIRED INFO: No Required Info

LDRV-5-MSGLENGTHINVLD

SEVERITY: Warning

FORMAT: "Invalid Message length, = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid CMM Message length on this receive queue. Line Drive discarded the message."

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

REQUIRED INFO: No Required Info

LDRV-5-CARDSTATEINVLD

SEVERITY: Warning

FORMAT: "Invalid card state set request, %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "CMM requests to set an invalid card state. Line Drive discarded the message."

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

REQUIRED INFO: No Required Info

LDRV-5-APPLTYPEINVLD

SEVERITY: Warning

FORMAT: "Invalid Message request type, %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "CMM requests an invalid message type. Line Drive discard the message."

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

REQUIRED INFO: No Required Info

LDRV-5-MSGSRCIDINVLD

SEVERITY: Warning

FORMAT: "Message from an unexpected source, %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Message from an unexpected source. Line Drive discard the message. "

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

REQUIRED INFO: No Required Info

LDRV-5-MISDIRECTEDMSG

SEVERITY: Warning

FORMAT: "Misdirected message, %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " Message is not intented for Ldrv is detected. Line Drive discard the message."

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

REQUIRED INFO: No Required Info

LDRV-4-RCVMSGFAILED

SEVERITY: Error

FORMAT: "Unable to receive message in the message queue"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SSI receive message routine detected an error. Message is being lost."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-MIBCNFMISMATCH

SEVERITY: Error

FORMAT: "HW card types don't match MIB cfg HW=%s, MIB= %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " DC and C type did not matched with the MIB config type This cold happen when user is swapping different line cards. Line Drver will use default configuration."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-SONETLINEINVLD

SEVERITY: Error

FORMAT: "Invalid sonetLine/sonetCfg Number %d in Config data base. Expected lineNum= %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Sonet Line number does not match with the configuration data base."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-SCRAMOPTINVLD

SEVERITY: Error

FORMAT: "Invalid frameScrambling option = %d in Config data base"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid SONET Scrambling option is detected in the configuration. It has to be either enabled or disabled. Line Driver will reset config to default value."

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

REQUIRED INFO: No Required Info

LDRV-4-SONETMEDINVLD

SEVERITY: Error

FORMAT: "Invalid sonet medium %d in BRAM is detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid SONET medium is detected in the configuration. Line Drive will reset config to default value."

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

REQUIRED INFO: No Required Info

LDRV-4-SECTRACEINVLD

SEVERITY: Error

FORMAT: "Invalid secton Trace Number %d in Config data base is detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid secton Trace Number is detected in the configuration Line Drive will reset config to default value."

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

REQUIRED INFO: No Required Info

LDRV-4-ALMSERVINVLD

SEVERITY: Error

FORMAT: "Invalid statSeverity/lineAlmCfg %d in Config data base is detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid statSeverity/lineAlmCfg is detected in the configuration. Line Drive will reset config to default value."

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

REQUIRED INFO: No Required Info

LDRV-4-DS3LNINVLD

SEVERITY: Error

FORMAT: "Out of Range (1..255) dsx3LineLength= %d in Config data base is detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " dsx3LineLength is not in the range of 1..255 is detected. Line Drive will reset config to default value."

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

REQUIRED INFO: No Required Info

LDRV-4-DS3REDSERV

SEVERITY: Error

FORMAT: "Out of Range (minor..major) dsx3RedSeverity= %d in Config data base is detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "dsx3RedSeverity is not in the range of detected minor..major. Line Drive will reset config to default value."

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

REQUIRED INFO: No Required Info

LDRV-4-DS3LINEINVLD

SEVERITY: Error

FORMAT: "Invalid line number = %d in Config data base is detected. Expected LineNum=%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " dsx3LineLength is not in the range of 1..255 is detected. Line Drive will reset config to default value."

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

REQUIRED INFO: No Required Info

LDRV-4-DBREGISTERERR

SEVERITY: Error

FORMAT: "Fail to registering %s data base, type = %d, version= %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " Unable to register the Line Driver data base. Ldrv task will not be able to spawn 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

LDRV-4-DBTBLERROR

SEVERITY: Error

FORMAT: "Fail to register TBL %s, NumElm=%d, ElmSize=%d, Upgrd=0x%p,dwngrd=0x%p"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " Unable to register an table entryin to the database. Ldrv task will not be able to spawn 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

LDRV-4-DBTBLIDINVLD

SEVERITY: Error

FORMAT: "%s Table %s is invalid. Table type=%d, Line Number=%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to read/update data base entry because of invalid table ID. Ldrv task will not be able to spawn 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

LDRV-4-DBMISMATCH

SEVERITY: Error

FORMAT: "Database does not matched with the line type =%d. Default the configuration"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The database has information that conflict with the current Back card type. We default the configuration now."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-PLPPDS3LNINVLD

SEVERITY: Error

FORMAT: "In Function %s, Line number %d, is invalid (Not in range of 1..2)"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to read/write DSx3 PLPP register because of invalid line number."

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

REQUIRED INFO: No Required Info

LDRV-4-PLPPOC3LNINVLD

SEVERITY: Error

FORMAT: "In Function %s, Line number %d, is invalid (Not in range of 1..2)"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to read/write OC3 PLPP register because of invalid line number."

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

REQUIRED INFO: No Required Info

LDRV-4-PLPPOC12LNINVLD

SEVERITY: Error

FORMAT: "In Function %s, Line number %d, is invalid (Not in range of 1..2)"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to read/write OC12 PLPP register because of invalid line number."

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

REQUIRED INFO: No Required Info

LDRV-4-CLKIMPINVLD

SEVERITY: Error

FORMAT: "External Clock impedance = %d is invalid"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "External Clock impedance is invalid. Expected value is 75 or 120 Ohms."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-CLKCONNINVLD

SEVERITY: Error

FORMAT: "External Clock connector type = %d is invalid"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "External Clock connector type is invalid. Expected value is RJ45 or SMB."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-CLKINBAND1INVLD

SEVERITY: Error

FORMAT: "Inband recovered Clock line number = %d is invalid"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Innband recovered clock has line number 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: No Required Info

LDRV-4-CLKINBAND2INVLD

SEVERITY: Error

FORMAT: "Inband Frame Pulse Clock has line number = %d is invalid"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Innband Frame Pulse Clock has line number 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: No Required Info

LDRV-4-CLKOPTINVLD

SEVERITY: Error

FORMAT: "Requested Inband Frame Pulse Clock source = %d but configuration doesn't allow it"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Requested Inband Frame Pulse Clock source but configuration doesn't allow it."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-CLKSRCUNKNOWN

SEVERITY: Error

FORMAT: "Unable to config requested clock source because clock source %d is unknown"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to config requested clock source because clock source is unknown."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-CLKMUXUNKNOWN

SEVERITY: Error

FORMAT: "Unable to config requested clock source because clock MUX %d is unknown"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unable to config requested clock source because clock MUX is unknown."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-4-CLKSRCCHANGE

SEVERITY: Error

FORMAT: "Current Clock source changed to %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Line Driver Clock source changed the current clock source seletion."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-7-CLKSETREQ

SEVERITY: Information

FORMAT: "Clock config Set for %s clock source"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "A snmp config set request is made to the clock module to switch clock."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

LDRV-7-SETIFERR

SEVERITY: Information

FORMAT: "Set Interface Type for Port = %d with invalid type %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "A request to set interface type with invalid ifType."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

LDRV-4-INVALID_PARMS

SEVERITY: Error

FORMAT: "QUNI Invalid Parameters %s, %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameters passed into function."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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

LDRV-6-QUNI_CFG_COND

SEVERITY: Notice

FORMAT: "QUNI chip Cfg for all lines, MIB_OBJ %s,%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Some of QUNI chip config params apply to all line, even when a change is effected through one mib object"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

DDTS "pxm-connmgm"

LDRV-3-DBNUMLINEINVLD

SEVERITY: Minor Alert

FORMAT: "Function= %s Line number %d..%d exceeded Max %d Line per PSM"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Config update function detected number of requested lines exceed the maximum number of line in the PSM"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-DBVERSIONINVLD

SEVERITY: Minor Alert

FORMAT: "Invalid Database version detected for %s, from%d.%d to%d.%d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unable to update the configuration data base because the invalid DB version number"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-PORTNUMINVLD

SEVERITY: Minor Alert

FORMAT: "%sInvalid Port number %d"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Invalid Port number passed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-UNKNOWNDCTYPE

SEVERITY: Major Alert

FORMAT: "In function %s Unknown Daughter card type %d is detected"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "The pio does not indicate a known daughter card type"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-RCMPCONINVLD

SEVERITY: Major Alert

FORMAT: "Invalid RCMP connection size %d for the DC card = %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "The DC identification bits are invalid for number of RCMP connection"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-FPGADNLDERR

SEVERITY: Major Alert

FORMAT: "Fpga download on card ID = %d failed"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "System routine to download FPGA image on a card returns fail"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-BCDCMISMATCH

SEVERITY: Major Alert

FORMAT: "Back Card and Daughter card types do not match BC=%d, DC=%d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Back card and Daughter card types do not match"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-LINEALARMCHG

SEVERITY: Notice

FORMAT: "Line Alarm on , port = %d, severity = %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Line alarm has been switched to a new state. The severity can be Major, Minor or Clear"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-LINESTATALARM

SEVERITY: Notice

FORMAT: "Statistical Alarm on Port %d, severity =%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Statistical alarm has been switched to a new state. The severity can be Major, Minor or Clear"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-PLCPALARM

SEVERITY: Notice

FORMAT: "Plcp Alarm on Port %d, severity =%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Plcp alarm has been switched to a new state. The severity can be Major, Minor or Clear"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-PLCPSTATALARM

SEVERITY: Notice

FORMAT: "Plcp Statistical Alarm on Port %d, severity =%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Plcp alarm has been switched to a new state. The severity can be Major, Minor or Clear"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-7-CARDTYPEACTION

SEVERITY: Information

FORMAT: "%s of type %s , %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Back card or Daughter card inserted"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CARDUNKNOWNINS

SEVERITY: Minor Alert

FORMAT: "%s of type %s , %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unknown Back card or Daughter card inserted."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-CARDREMOVED

SEVERITY: Major Alert

FORMAT: "%s of type %s , %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "BC or DC removed Line Driver enters Fail state if BC or DC is removed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-UNKNOWNBCTYPE

SEVERITY: Major Alert

FORMAT: "Unknown Backcard card %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "The NOVRAM read from the card does not have a valid backcard type The Line Driver enters Fail state until a valid back card is inserted"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-RCMPRSTFAIL

SEVERITY: Major Alert

FORMAT: "RCMP reset Failed for DC type %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "RCMP reset fail for the specified Daughter card. Line Driver enters Fail state"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-MSGLENGTHINVLD

SEVERITY: Warning

FORMAT: "Invalid Message length, = %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Invalid CMM Message length on this receive queue Message discarded by Line Driver"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-CARDSTATEINVLD

SEVERITY: Warning

FORMAT: "Invalid card state set request, %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " CMM requests to set an invalid card state Message discarded by Line Driver"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-APPLTYPEINVLD

SEVERITY: Warning

FORMAT: "Invalid Message request type, %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Invalid message type sent by CMM Message discarded by Line Driver"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-MSGSRCIDINVLD

SEVERITY: Warning

FORMAT: "Message from an unexpected source, %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Message from an unexpected source Message discarded by Line Driver"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-MISDIRECTEDMSG

SEVERITY: Warning

FORMAT: "Misdirected message, %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Message detected not intended for Line Driver. Message discarded by Line Driver"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-RCVMSGFAILED

SEVERITY: Minor Alert

FORMAT: "Unable to receive message in the message queue"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Expected message not available in SSI receive queue Message is being lost"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-MIBCNFMISMATCH

SEVERITY: Major Alert

FORMAT: "HW card types do not match MIB cfg HW=%s, MIB= %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " DC and BC type do not match the MIB config type This could happen when user swaps different line cards Line Driver will use default configuration"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-SONETLINEINVLD

SEVERITY: Minor Alert

FORMAT: "Invalid sonetLine/sonetCfg Number %d in Config data base. Expected lineNum= %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Sonet Line number does not match with the configuration data base"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-SCRAMOPTINVLD

SEVERITY: Minor Alert

FORMAT: "Invalid frameScrambling option = %d in Config data base"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Invalid SONET Scrambling option is detected in the configuration It has to be either enable or disable Line Driver will reset config to default value "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-SONETMEDINVLD

SEVERITY: Minor Alert

FORMAT: "Invalid sonet medium %d in BRAM is detected"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Invalid SONET medium detected in the configuration Line Driver will reset config to default value "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-SECTRACEINVLD

SEVERITY: Minor Alert

FORMAT: "Invalid secton Trace Number %d in Config data base is detected"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Invalid secton Trace Number detected in the configuration Line Driver will reset config to default value "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-ALMSERVINVLD

SEVERITY: Minor Alert

FORMAT: "Invalid statSeverity/lineAlmCfg %d in Config data base is detected"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Invalid statSeverity/lineAlmCfg detected in the configuration Line Driver will reset config to default value "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-DS3LNINVLD

SEVERITY: Minor Alert

FORMAT: "Out of Range (1..255) dsx3LineLength= %d in Config data base"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " dsx3LineLength is not in the range of 1..255 Line Driver will reset config to default value "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-DS3REDSERV

SEVERITY: Minor Alert

FORMAT: "Out of Range (minor..major) dsx3RedSeverity= %d in Config data base "

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "dsx3RedSeverity is not in the range of minor..major Line Driver will reset config to default value "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-DS3LINEINVLD

SEVERITY: Minor Alert

FORMAT: "Invalid line number = %d in Config data base. Expected LineNum=%d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " dsx3LineLength is not in the range of 1..255 Line Driver will reset config to default value "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-DBREGISTERERR

SEVERITY: Minor Alert

FORMAT: "Failed to register %s data base, type = %d, version= %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to register the Line Driver data base Ldrv task will not be able to spawn properly"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-DBTBLERROR

SEVERITY: Minor Alert

FORMAT: "Failed to register TBL %s, NumElm=%d, ElmSize=%d, Upgrd=0x%p,dwngrd=0x%p"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to register a table entry into the database Ldrv task will not be able to spawn properly"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-DBTBLIDINVLD

SEVERITY: Minor Alert

FORMAT: "%s Table %s is invalid. Table type=%d, Line Number=%d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unable to read/update data base entry because of invalid table ID Ldrv task will not be able to spawn properly"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-DBMISMATCH

SEVERITY: Minor Alert

FORMAT: "Database does not match the line type =%d. Use default configuration"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "The database has information that conflicts with the current Back card type... Using the default configuration "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-PLPPDS3LNINVLD

SEVERITY: Major Alert

FORMAT: "In Function %s, Line number is invalid (Not in range of 1..2)"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unable to read/write DSx3 PLPP register because of invalid line number"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-PLPPOC3LNINVLD

SEVERITY: Major Alert

FORMAT: "In Function %s, Line number is invalid (Not in range of 1..2)"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unable to read/write OC3 PLPP register because of invalid line number"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-PLPPOC12LNINVLD

SEVERITY: Major Alert

FORMAT: "In Function %s, Line number is invalid (Not in range of 1..2)"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unable to read/write OC12 PLPP register because of invalid line number"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CLKIMPINVLD

SEVERITY: Minor Alert

FORMAT: "External Clock impedance = %d is invalid"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "External Clock impedance is invalid. Expected value is 75 or 120 Ohms"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CLKCONNINVLD

SEVERITY: Minor Alert

FORMAT: "External Clock connector type = %d is invalid"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "External Clock connector type is invalid. Expected value is RJ45 or SMB"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CLKINBAND1INVLD

SEVERITY: Minor Alert

FORMAT: "Inband recovered Clock line number = %d is invalid"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Inband recovered clock has invalid line number."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CLKINBAND2INVLD

SEVERITY: Minor Alert

FORMAT: "Inband Frame Pulse Clock line number = %d is invalid"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Inband Frame Pulse Clock has invalid line number"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CLKOPTINVLD

SEVERITY: Minor Alert

FORMAT: "Requested Inband Frame Pulse Clock source = %d but configuration doesn't allow it"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Requested Inband Frame Pulse Clock source not allowed by configuration"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CLKSRCUNKNOWN

SEVERITY: Minor Alert

FORMAT: "Unable to config requested clock source because clock source %d is unknown"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to config requested clock source because clock source is unknown"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CLKMUXUNKNOWN

SEVERITY: Minor Alert

FORMAT: "Unable to config requested clock source because clock MUX %d is unknown"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to config requested clock source because clock MUX is unknown"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CLKSRCCHANGE

SEVERITY: Minor Alert

FORMAT: "Current Clock source changed to %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Line Driver Clock source changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-7-CLKSETREQ

SEVERITY: Information

FORMAT: "Clock config Set for %s clock source"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " A snmp config set request made to the clock module to switch clock "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-7-SETIFERR

SEVERITY: Information

FORMAT: "Set Interface Type for Port = %d with invalid type %d "

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " A request to set interface type with invalid ifType"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-IPCREATERR

SEVERITY: Warning

FORMAT: "IPC create failed"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to create IPC end point."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-IPCNAMEBINDERR

SEVERITY: Warning

FORMAT: "Error binding name %s to Epid 0x%x"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to bind name to IPC end point."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-IPCHANDLERERR

SEVERITY: Warning

FORMAT: "IPC handler attach failed"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to attach handler to IPC end point."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-ADDLNERR

SEVERITY: Major Alert

FORMAT: "Addln failed"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to add line."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-LDRV10MSTASKSPA

SEVERITY: Major Alert

FORMAT: "Ldrv 10ms task spawn failed"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to spawn 10ms task."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-UPIFERR

SEVERITY: Major Alert

FORMAT: "Upif failed"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Unable to add Virtual Interface."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-LMIALARMSETTRAP

SEVERITY: Major Alert

FORMAT: "lDrv LMI Alarm Set Trap send"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Loss of LMI on trunk."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-LMIALARMCLEARTR

SEVERITY: Notice

FORMAT: "lDrv LMI Alarm Clear Trap send"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: " Loss of LMI on trunk has been cleared."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-CTCTRANSFAIL

SEVERITY: Minor Alert

FORMAT: "LDRV transition to %s failed "

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Line Driver unable to transition to said state"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-5-INVALID_PARMS

SEVERITY: Warning

FORMAT: "QUNI Invalid Parameters %s, %d"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Invalid parameters passed into function"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-QUNI_CFG_CONDIT

SEVERITY: Notice

FORMAT: "QUNI chip Cfg for all lines, MIB_OBJ %s,%d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Some of QUNI chip config params apply to all line, even when a change is effected through one mib object"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-WRONG_US_REQ

SEVERITY: Notice

FORMAT: "Receive a wrong user APS request [%s]"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Receive a wrong user APS request"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-4-WRONG_RM_REQ

SEVERITY: Error

FORMAT: "Receive a wrong remote APS request [%s]"

FLAG: Dump Trace

THROTTLING: One Second

EXPLANATION: "Receive a wrong remote APS request"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-4-WRONG_IN_REQ

SEVERITY: Error

FORMAT: "Receive a wrong internal APS request [%s]"

FLAG: Stack Trace | Dump Trace

THROTTLING: One Second

EXPLANATION: "Receive a wrong internal APS request"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-2-IN_FAILURE

SEVERITY: Major Alert

FORMAT: "Internal failure upon APS request [%s]"

FLAG: Stack Trace | Dump Trace

THROTTLING: One Second

EXPLANATION: "Internal failure observed upon issuing APS request"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-4-NON_UNI_REQ

SEVERITY: Error

FORMAT: "Non_unidirection request in unidirection mode [%s]"

FLAG: Dump Trace

THROTTLING: One Second

EXPLANATION: "Receive non_unidirection request in unidirection mode"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-4-UN_EXPT_REQ

SEVERITY: Error

FORMAT: "Unexpected APS request [%s]"

FLAG: Dump Trace

THROTTLING: One Second

EXPLANATION: "Unexpected APS request received"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-4-PIPC

SEVERITY: Error

FORMAT: "Error when using PIPC [%s]"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Error when using PIPC"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-4-UNEX_PIPC_MSG

SEVERITY: Error

FORMAT: "Unexpected PIPC message[%d]"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Unexpected PIPC message"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-4-NULL_PIPC_MSG

SEVERITY: Error

FORMAT: "NULL PIPC message"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "NULL PIPC message"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-UNEX_CLI_CM

SEVERITY: Notice

FORMAT: "Received an unexpected cli command [%s]"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Received an unexpected cli command"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-APS_SWITCH

SEVERITY: Notice

FORMAT: "APS switch from line %d.%d to line %d.%d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS switching"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-APS_SWITCH2

SEVERITY: Notice

FORMAT: "APS switch from line %d.%d to line %d.%d due to request %s from %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS switching with switching reason"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-APS_SWITCH_FAIL

SEVERITY: Notice

FORMAT: "APS %s switch failure from line %d.%d to line %d.%d by %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS switching Failure"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-APS_LINE_FAILUR

SEVERITY: Minor Alert

FORMAT: "Working line of line %d in APS pair fails"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS line failure"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-APS_PLINE_FAILU

SEVERITY: Minor Alert

FORMAT: "Protection line of line %d in APS pair fails"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS protection line failure"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-APS_LINE_CLEAR

SEVERITY: Notice

FORMAT: "Working line of line %d in APS pair is clear"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS alarm on line cleared"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-APS_PLINE_CLEAR

SEVERITY: Notice

FORMAT: "Protection line of line %d in APS pair is clear"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS protection line is clear"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-APS_USER_CLR

SEVERITY: Notice

FORMAT: "APS user clear request"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS user clear request"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-APS_USER_LOCK

SEVERITY: Notice

FORMAT: "APS user lock request"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "APS user lock request"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-6-LDRV_CD_EVT_ERR

SEVERITY: Notice

FORMAT: "Card Event Error [%s]"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Card Event Error"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-1-VC_CON_FAIL

SEVERITY: Fatal

FORMAT: "VcConSetup failed for card in slot "

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "VcConSetup function failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LDRV-3-LDRV_DID_NOT_RU

SEVERITY: Minor Alert

FORMAT: "lDrv10msTask did not run for the past %d ticks "

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "line driver task did not run for the past 1 second "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "sys/uplink"

LMI-4-SWERROR

SEVERITY: Error

FORMAT: "SOFTWARE ERROR <%d> %d %d %d %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-7-LMI_DEBUG_EVENT

SEVERITY: Information

FORMAT: "\n*****FUNCTION %s %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-7-FEEDER_EVENT

SEVERITY: Information

FORMAT: "%s on TRK %d, %d %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_LMI_PORT

SEVERITY: Error

FORMAT: "%s An invalid logical LMI port Id was identified"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-SEM_CREATE_ERR

SEVERITY: Error

FORMAT: "%s An error in creating a semaphore was detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_LMI_IFNUM

SEVERITY: Error

FORMAT: "%s An invalid logical physical interface Id was identified"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-BAD_IP_ADDR

SEVERITY: Warning

FORMAT: "%s An error was detected in getting the shelf IP address"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_FDR_CODE

SEVERITY: Error

FORMAT: "%s An invalid feeder function code was identified"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_MSG_REV

SEVERITY: Error

FORMAT: "%s An invalid feeder message revision was identified"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_MEM_ALLOC

SEVERITY: Error

FORMAT: "%sLine #%d A memory allocation error was detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_PTR

SEVERITY: Error

FORMAT: "%sLine #%d An invalid NULL pointer was detected"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-BAD_CASE_EVENT

SEVERITY: Warning

FORMAT: "%sLine #%d An invalid event %d within a case statement was detected"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-GET_BULK_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in getting bulk SPC status information"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-GET_RING_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in getting SPC status from the queue"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-GET_SHELF_NM

SEVERITY: Error

FORMAT: "%s An error was detected in getting the shelf node name"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-GET_SHELF_IP

SEVERITY: Warning

FORMAT: "%s An error was detected in getting the shelf LAN IP address"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-GET_SHELF_MOD_N

SEVERITY: Error

FORMAT: "%s An error was detected in getting the shelf model number"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-GET_SLOT_PORT

SEVERITY: Warning

FORMAT: "%s An error was detected in getting the slot/port number"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-ADD_LMI_CHAN

SEVERITY: Warning

FORMAT: "%s An error was detected in adding a LMI channel"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-DEL_LMI_CHAN

SEVERITY: Warning

FORMAT: "%s An error was detected in deleting a LMI channel"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-LMI_SIG_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in configuring the LMI signalling chan"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-ABIT_CLR_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in clearing A-bit alarms"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-MSG_SEND_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in sending a msg to the ext interface"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-MSG_ISEND_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in sending a msg to the int interface"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-MSG_IPSEND_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in sending a msg to the IP int interface"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-IMSG_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in forming a msg to the int interface"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-SEM_GET_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in gettting a semaphore"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-LCN_BIND_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in establishing an external connection"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-EP_CREATE_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in creating a communication endpoint"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-EP_NAME_BIND

SEVERITY: Error

FORMAT: "%s An error was detected in binding a name to a endpoint"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-EP_NAME_UNBIND

SEVERITY: Warning

FORMAT: "%s An error was detected in unbinding a name to a endpoint"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-EP_HNDLR_BIND

SEVERITY: Error

FORMAT: "%s An error was detected in binding a handler to a endpoint"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-EP_RESLV_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in resolving the redundant endpoint"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-GET_LSLOT_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in getting the logical slot number"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-GET_PSLOT_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in getting the physical slot number"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-STDBY_RDY_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in going to a standby ready state"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-NO_PROVSN_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in going to a no provision state"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-ACTIVE_RDY_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in going to a active ready state"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-QUIESCENT_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in going to quiescent state"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-CTC_INIT_DONE_E

SEVERITY: Error

FORMAT: "%s An error was found notifying CTC about completing init"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-CTC_ACTV_RDY_ER

SEVERITY: Warning

FORMAT: "%s An error was found notifying CTC about active ready state"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-CTC_STDBY_RDY_E

SEVERITY: Error

FORMAT: "%s An error was found notifying CTC about standby ready state"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-BAD_STNDBY_MSG

SEVERITY: Warning

FORMAT: "%s An invalid message was received while in a standby state"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-BAD_LMI_STATE

SEVERITY: Warning

FORMAT: "%sLine #%d An invalid LMI state transition was detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_DISK_IMAGE

SEVERITY: Error

FORMAT: "%s An error was detected in reading info from the system disk"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-INT_MSG_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected sending an internal message%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-REGISTER_DB

SEVERITY: Warning

FORMAT: "%s An error was detected registering the disk database"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-MAX_NS_MSG_ERR

SEVERITY: Warning

FORMAT: "%s The maximum number of node status messages has been exceeded"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-MAX_SPC_MSG_ERR

SEVERITY: Warning

FORMAT: "%s The maximum number of SPC status messages has been exceeded"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-SPC_CNT_ERR

SEVERITY: Warning

FORMAT: "%s An invalid SPC status message count has been detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-GET_IFC_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in getting an ifnum for a LCN value"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-TASK_SPAWN_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in spawning a LMI task"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-DISKDB_REG_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in registering with the disk DB"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-TIMEOUT_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in scheduling a timeout"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-TIMER_CREATE_ER

SEVERITY: Error

FORMAT: "%s An error was detected in creating a timer"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-EP_TIMEOUT_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in waiting for an endpoint timeout"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_TASK_INDEX

SEVERITY: Error

FORMAT: "%s An invalid LMI task index was identified"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-IP_MSG_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in sending Node Status to IP conn"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-REGISTER_IFNUM

SEVERITY: Warning

FORMAT: "%s An error was detected registering the logical physical ifnum"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-7-SYNCRAM_RESET

SEVERITY: Information

FORMAT: "%s A syncram reset was detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-7-SYNCRAM_RESET_C

SEVERITY: Information

FORMAT: "%s A syncram reset was detected! Cause %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-UNKNOWN_RAMDB

SEVERITY: Warning

FORMAT: "%s An unknown RAM database was detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-RCV_RDY_ERR

SEVERITY: Error

FORMAT: "%s A problem was detected sending a DB Rx Ready event"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-SYNC_DONE_ERR

SEVERITY: Error

FORMAT: "%s A problem was sending a sync done msg to the standby card"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-LMI_DEBUG_ERR

SEVERITY: Warning

FORMAT: "%s Line %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-LMI_BADSTATE_ER

SEVERITY: Error

FORMAT: "%s Command %d was sent in an invalid LMI state %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-LMI_BADCMD_ERR

SEVERITY: Error

FORMAT: "%s An invalid command %d was received"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-LMI_BADRESP_ERR

SEVERITY: Error

FORMAT: "%s An invalid LMI response %d for command %d was received"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "sys/uplink"

LMI-4-CPRO_GET_OP_STA

SEVERITY: Error

FORMAT: "%s cPro Get OperState Fails, ifNum=%d"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "feeder-lmi"

LMI-4-SWERROR

SEVERITY: Error

FORMAT: "SOFTWARE ERROR <%d> %d %d %d %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "This problem occured due to an internal error"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-7-LMI_DEBUG_EVENT

SEVERITY: Information

FORMAT: "\n*****FUNCTION %s %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_LMI_PORT

SEVERITY: Error

FORMAT: "%s An invalid logical LMI port Id was identified"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "This problem occured because an invalid LMI port Id was identified. This will not affect traffic"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-SEM_CREATE_ERR

SEVERITY: Error

FORMAT: "%s An error in creating a semaphore was detected"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error in creating a semaphore was detected.This is an internal error."

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

REQUIRED INFO:

LMI-4-BAD_LMI_IFNUM

SEVERITY: Error

FORMAT: "%s An invalid logical physical interface Id was identified"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An invalid logical physical interface Id was identified"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-BAD_IP_ADDR

SEVERITY: Error

FORMAT: "An error was detected in getting the %s IP address"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An error was detected in getting the shelf IP address"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-5-BAD_FDR_CODE

SEVERITY: Warning

FORMAT: "%s An invalid feeder function code was identified"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-BAD_MSG_REV

SEVERITY: Warning

FORMAT: "%s An invalid feeder message revision was identified"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-BAD_MEM_ALLOC

SEVERITY: Error

FORMAT: "%sLine #%d A memory allocation error was detected"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "This can happen if an error was detected while allocating memory"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-BAD_PTR

SEVERITY: Error

FORMAT: "%sLine #%d An invalid NULL pointer was detected"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An invalid NULL pointer was detected"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-5-BAD_CASE_EVENT

SEVERITY: Warning

FORMAT: "%sLine #%d An invalid event %d within a case statement was detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-GET_BULK_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in getting bulk SPC status information"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-GET_RING_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in getting SPC status from the queue"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An error was detected in accessing the update queue. This will not affect traffic"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-GET_SHELF_NM

SEVERITY: Error

FORMAT: "%s An error was detected in getting the shelf node name"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An error was detected in getting the shelf node name"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-GET_SHELF_IP

SEVERITY: Error

FORMAT: "%s An error was detected in getting the shelf LAN IP address"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An error was detected in getting the shelf LAN IP address"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-GET_SHELF_MOD_N

SEVERITY: Error

FORMAT: "%s An error was detected in getting the shelf model number"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An error was detected in getting the shelf model number"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-ADD_LMI_CHAN

SEVERITY: Error

FORMAT: "%s An error was detected in adding a LMI channel"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in adding a LMI channel"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-DEL_LMI_CHAN

SEVERITY: Error

FORMAT: "%s An error was detected in deleting a LMI channel"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in deleting a LMI channel"

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:

LMI-4-LMI_SIG_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in configuring the LMI signalling chan"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in configuring the LMI signalling chan"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-5-ABIT_CLR_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in clearing A-bit alarms"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-MSG_SEND_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in sending a msg to the ext interface"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in sending a msg to the ext interface"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-MSG_ISEND_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in sending a msg to the int interface"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in sending a msg to the int interface"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-MSG_IPSEND_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in sending a msg to the IP int interface"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in sending a msg to the IP int interface"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-IMSG_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in forming a msg to the int interface"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in forming a msg to the int interface"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-SEM_GET_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in gettting a semaphore"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected getting a semaphore"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-LCN_BIND_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in establishing an external connection"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in establishing an external connection"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-EP_CREATE_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in creating a communication endpoint"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: " An error was detected in creating a communication endpoint. "

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-EP_NAME_BIND

SEVERITY: Error

FORMAT: "%s An error was detected in binding a name to a endpoint"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in binding a name to a endpoint"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-EP_NAME_UNBIND

SEVERITY: Error

FORMAT: "%s An error was detected in unbinding a name to a endpoint"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in unbinding a name to a endpoint"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-EP_HNDLR_BIND

SEVERITY: Error

FORMAT: "%s An error was detected in binding a handler to a endpoint"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in binding a handler to a endpoint"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-STDBY_RDY_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in going to a standby ready state"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An error was detected in going to a standby ready state"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-NO_PROVSN_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in going to a no provision state"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in going to a no provision state"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-ACTIVE_RDY_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in going to a active ready state"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in going to a active ready state"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-QUIESCENT_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in going to quiescent state"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in going to quiescent state"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-CTC_INIT_DONE_E

SEVERITY: Error

FORMAT: "%s An error was found notifying CTC about completing init"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was found notifying CTC about completing init"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-CTC_ACTV_RDY_ER

SEVERITY: Error

FORMAT: "%s An error was found notifying CTC about active ready state"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was found notifying CTC about active ready state"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-CTC_STDBY_RDY_E

SEVERITY: Error

FORMAT: "%s An error was found notifying CTC about standby ready state"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was found notifying CTC about standby ready state"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-5-BAD_STNDBY_MSG

SEVERITY: Warning

FORMAT: "%s An invalid message was received while in a standby state"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

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

LMI-5-BAD_LMI_STATE

SEVERITY: Warning

FORMAT: "%sLine #%d An invalid LMI state transition was detected"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

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

LMI-4-BAD_DISK_IMAGE

SEVERITY: Error

FORMAT: "%s An error was detected in reading info from the system disk"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in reading info from the system disk"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-5-INT_MSG_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected sending an internal message%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected sending an internal message"

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

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-5-MAX_NS_MSG_ERR

SEVERITY: Warning

FORMAT: "%s The maximum number of node status messages has been exceeded"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The maximum number of retries to send node status messages to the standby has been exceeded"

RECOMMENDED ACTION: "Check if standby card (dspcds/dspcd) is in READY state"

REQUIRED INFO: No Required Info

LMI-5-MAX_SPC_MSG_ERR

SEVERITY: Warning

FORMAT: "%s The maximum number of SPC status messages has been exceeded"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-SPC_CNT_ERR

SEVERITY: Warning

FORMAT: "%s An invalid SPC status message count has been detected"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-5-GET_IFC_ERR

SEVERITY: Warning

FORMAT: "%s An error was detected in getting an ifnum for a LCN value"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

LMI-4-TASK_SPAWN_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in spawning a LMI task"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: " An error was detected in spawning a LMI task"

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

REQUIRED INFO: Please capture the following information from the PXM45 cli and call your TAC support

1) dspcds/dspcd

2) dspver

3) dsplog -sl <slot which is experiencing the problem>

4) dsplog -sl < redundant slot if configured>

5) dsperr for the above slots.

6) Save the core file if required

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-DISKDB_REG_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in registering with the disk DB"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An error was detected in registering with the disk DB"

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

Collect the following information from the slot on which the error occured

a) dsplmis/dslmi

b) dspports /dspport

c) dsplns

LMI-4-TIMEOUT_ERR

SEVERITY: Error

FORMAT: "%s An error was detected in scheduling a timeout"

FLAG: Stack Trace

THROTTLING: One Tick