Table Of Contents

Error Messages for MGX and SES Release 4.0.00

ACAR-2-SHLFINIT

ACAR-2-SHLFINIT_ENDPT

ACAR-2-DBINIT

DDTS "pxm-connmgm"

CM_L-7-CM_LMI_NO_ALM_C

CM_L-7-CM_LMI_INIT_SUC

CM_L-4-CM_LMI_MEM_ERRO

CM_L-4-CM_LMI_ERR_GEN

CM_L-5-CM_LMI_ERR_SLOT

CM_L-2-CM_LMI_ERR_PORT

CM_L-4-CM_LMI_ERR_MSGQ

CM_L-5-CM_LMI_ERR_SET_

CM_L-4-CM_LMI_ERR_SCHE

CM_L-4-CM_LMI_CREATE_T

CM_L-5-CM_LMI_LSLOT_ER

CM_L-5-CM_LMI_PSLOT_ER

DDTS "pxm-connmgm"

ACAR-2-SHLFINIT

ACAR-2-SHLFINIT_ENDPT

ACAR-2-DBINIT

ACAR-2-SMM_ERROR_GEN

ACAR-4-MSG_PROC_ERR

ACAR-4-CHK_ERR

ACAR-7-INFO_LOG

DDTS "shm"

RED-7-DETECT_MISMATCH

RED-7-MSG_DATA_ERROR

RED-7-AC_SEND_MSG_ERR

RED-7-AC_GEN_ERR

RED-4-NACK_ERR

RED-7-AC_INFO_ERR

RED-7-TBL_UPD_INFO

RED-7-AC_SWITCHCARD_I

RED-7-AC_MEM_ERR

RED-7-AC_TIME_OUT_ERR

RED-7-AC_WRNGMSG_ERR

RED-7-AC_DWNLBRAMERR

RED-7-AC_UPLDBRAMERR

RED-7-BADARCERR

RED-7-SMM_ERROR_GEN

RED-7-SMM_INFO

RED-7-SMM_GEN_ERR

RED-7-BAD_SHLF_SLOT

RED-7-RAM_SYNC_IOV_FA

RED-7-RAM_SYNC_IOV_SE

RED-4-MSGQ_BIND_FAIL

RED-4-IPC_COM_EPID_FA

RED-4-PIPC_PORT_CREAT

RED-4-INIT_TBL_FAILED

RED-7-SM_MSG_RCVD

RED-6-AC_INCORRECT_ST

RED-6-AC_INVALID_MSG

RED-4-DOWNLOAD_FAILED

RED-7-DOWNLOAD_PASSED

RED-7-PMM_MSG_RCVD

RED-4-CD_STATE_MISMAT

RED-7-PMM_EVENT_SET

RED-7-SM_STATE_EVENT

RED-5-SM_STATE_CHANGE

RED-7-SM_INVALID_EVEN

RED-5-SEND_MISMATCH_M

RED-5-IPC_MSG_RVC_ERR

RED-5-SSI_RCVID_ERROR

RED-5-IPC_MSG_ALLOC_F

RED-5-IPC_MSG_REPLY_F

RED-5-CLI_INVALID_PAR

RED-5-CLI_NULL_PARAM

RED-5-IPC_MSG_SEND_FA

RED-5-IPC_DATAPTR_NUL

RED-4-RED_CMD_MISMATC

RED-7-INV_CLI_CMD

RED-5-FW_UPGD_FAIL

RED-5-CTC_INV_EVENT

RED-4-CD_REMOVED

RED-4-CD_FAILED

RED-7-AC_ADDRED_INFO

RED-7-AC_DELRED_INFO

RED-7-CD_STATE_INFO

RED-7-PRIMARY_NOT_PRO

RED-7-SEC_CD_INFO

RED-7-LINEMODULE_INFO

RED-7-AC_MIB_MISMATCH

RED-7-DWLD_INFO

RED-5-DWLD_FOPEN_FAIL

RED-4-DWLD_FAILED

RED-4-AC_INIT_FAIL

RED-5-AC_INIT_ERR

RED-7-AC_INIT_INFO

RED-7-REDUNDANCY_INFO

RED-4-PMM_CD_RESET

RED-5-SM_INSERT_MSG

RED-4-SM_FAILED_MSG

RED-4-SM_MISMATCH_MSG

RED-4-SM_REMOVED_MSG

RED-7-CARD_FAIL_INFO

RED-7-SHM_MSGRCV

RED-7-CMD_FAILED

DDTS "alarms"

CAMA-5-INVALIDINPUT

CAMA-5-PARMOUTOFTRANGE

CAMA-5-PARMINVALID

CAMA-5-PARMINVLENGTH

CAMA-5-FUNCFAIL_STKDUM

CAMA-5-QUEUEFULL

DDTS "unknown"

AUPL-5-INVD_INPT

AUPL-4-INVD_RET

AUPL-4-INVD_VAL

AUPL-4-INVD_STR

AUPL-4-INVD_INPT

AUPL-4-INVD_RET

AUPL-4-INVD_VAL

AUPL-4-INCRT_CALL

DDTS "axsm_apps"

APS-4-APS_MAIN_ERR

APS-4-APS_MUX_ERR

APS-4-INIT_ERR

APS-4-APS_MSG_ERR

APS-4-APS_IPC_COMEP_C

APS-4-APS_IPC_COMEP_U

APS-4-APS_IPC_COMEP_N

APS-4-APS_IPC_MSG_SEN

APS-4-APS_IPC_MSG_ALL

APS-4-APS_EM_REPORT_F

APS-4-APS_MSG_HNDLR_I

APS-4-APS_RMI_SEND_FA

APS-4-APS_RMI_CTXT_PU

APS-4-APS_RMI_USER_AC

APS-4-APS_RMI_ACKDATA

APS-4-APS_RMI_MSG_ALL

APS-4-APS_INVALID_CAR

APS-4-APS_RMI_LINE_PA

APS-4-APS_RMI_UNACK_D

APS-4-APS_RMI_SYNC_DA

APS-4-APS_RMI_RMT_EPI

APS-4-APS_UNKNOWN_MSG

APS-4-RMI_UNACK_DATAS

APS-4-APS_RMI_PORT_CR

APS-4-APS_INVALID_EPI

APS-4-APS_INVALID_CTC

APS-4-APS_RMT_BKCD_DE

APS-4-APS_RMT_FRONTCD

APS-4-APS_INVALID_CTC

APS-7-APS_AISL_DECL

APS-7-APS_PRDI

APS-7-APS_SF_DECL

APS-7-APS_SELECTOR_RE

APS-7-APS_PROT_LINE_S

APS-7-APS_BRIDGE_RELE

APS-7-APS_WORKCHAN_BR

APS-7-APS_TXK1

APS-7-APS_TXK2

APS-7-APS_RXK1

APS-7-APS_RXK2

APS-7-APS_PROVISION

APS-7-APS_DELETE

APS-7-APS_CONFIG_SF_B

APS-7-APS_CONFIG_SD_B

APS-7-APS_CONFIG_WTR

APS-7-APS_CONFIG_DIR

APS-7-APS_CONFIG_REV

APS-7-APS_USER_SWITCH

APS-7-APS_PSB_INVALCH

APS-7-APS_PSB_INVALCO

APS-7-APS_PSB_INCONSB

APS-7-APS_PSB_IRRELEV

APS-7-APS_PSB_FAILURE

APS-7-APS_PSBF_CLEARE

APS-7-APS_CHMM_CLEARE

APS-6-ADD_LN

APS-6-DEL_LN

APS-3-SW_CLEAR

APS-3-SW_LOCK

APS-3-SW_FORCE_WTOP

APS-3-SW_FORCE_PTOW

APS-3-SW_MAN_WTOP

APS-3-SW_MAN_PTOW

APS-2-PSB_FAIL

APS-2-CHAN_MISMATCH

APS-2-PRIM_SEC_MISMAT

APS-6-CNF_SFBER

APS-6-CNF_SDBER

APS-6-CNF_WTR

APS-6-CNF_DIR

APS-7-CNF_PROTO

APS-7-CNF_OPMODE

APS-7-APS_OPMODE_ERR

APS-6-CNF_REV

APS-3-SF_DECL

APS-3-SF_DECL_CLEAR

APS-3-SW_SERVICE

APS-4-PSBF_CLEARED

APS-4-CHAN_MIS_CLEARE

APS-2-FAR_END_FAIL

APS-2-FAR_END_FAIL_CL

APS-2-MODE_MISMATCH

APS-6-MODE_MIS_CLEAR

APS-4-SW_CLEAR_FAIL

APS-4-SW_LOCK_FAIL

APS-4-SW_FORCE_WTOP_F

APS-4-SW_FORCE_PTOW_F

APS-4-SW_MAN_WTOP_FAI

APS-4-SW_MAN_PTOW_FAI

APS-3-SD

APS-3-SD_CLEAR

APS-3-SW_SF

APS-3-SW_SD

APS-3-SW_REV

APS-3-SW_DONOT_REV

APS-3-SW_WTR

APS-3-SW_UNKNOWN

APS-4-SW_SF_FAIL

APS-4-SW_SD_FAIL

APS-4-SW_REV_FAIL

APS-3-SW_DONOT_REV_FA

APS-7-APS_CHMM_FAILUR

APS-4-APS_PHY_ERR

APS-4-APS_PHY_BAD_PAR

DDTS "unknown"

SSI-4-ARCH_ERROR

DDTS "pxm-connmgm"

SSI-4-ARCH_ERROR

DDTS "shm"

ENVM-4-ADC_CONV_ERROR

ENVM-4-ADC_ERROR

ENVM-2-ENV_ALARM_SET

ENVM-3-ENV_ALARM_CLR

ENVM-4-ENV_TRAP_GEN

ENVM-4-ENV_ERROR

DDTS "drivers/ccma"

ATLA-4-AT_INIT_ERR

ATLA-4-AT_INTRPT_ERR

ATLA-4-AT_GEN_ERR

ATLA-4-AT_PARAM_ERR

ATLA-4-AT_ACCESS_ERR

ATLA-4-AT_CONACC_ERR

DDTS "atmsig"

ATMC-5-INTERNAL_CRITIC

ATMC-5-P2MP_ERR

ATMC-5-P2MP_WARN

ATMC-7-P2MP_INFO

ATMS-4-ATMSIG_PRTY_INS

ATMS-4-ATMSIG_PRTY_DEL

ATMS-4-ATMSIG_SVC_INSE

ATMS-4-ATMSIG_SVC_DELE

ATMS-4-NOSVC

ATMS-4-NOCALLREF

ATMS-6-FAILHALFLEGREM

ATMS-4-FAIL2NDHALFLEG

ATMS-4-FAILXCONN

SCHE-4-UNEXPECTEDMESSA

SCHE-4-UNEXPECTEDEVENT

SCHE-4-UNEXPECTEDTIMER

DDTS "unknown"

ADDR-5-ADDR_ERROR

ADDR-7-ADDR_INFORMATIV

DDTS "ifm"

IFM-4-ERROR

IFM-5-WARNING

IFM-7-INFO

IFM-6-NOTICE

DDTS "atmsig"

VCM-6-LEG_CREATE

ATMC-5-INTERNAL_WARNIN

ATMC-5-SETCAC_WARN

ATMC-5-BITMAP_ERR

ATMC-5-BITMAP_WARN

ATMC-7-BITMAP_INFO

DDTS "atmsig"

TRAF-5-ADDFAIL

TRAF-5-DELFAIL

TRAF-5-NOABRPARM

TRAF-5-DBCREATEFAIL

TRAF-5-NULLPTR

TRAF-5-NULLELEPTR

TRAF-5-BADELE

TRAF-5-BADELECHKSUM

TRAF-5-BROKENLIST

TRAF-5-NOTINFREELIST

TRAF-5-NOTINUSE

TRAF-5-NOTALLOC

TRAF-5-CANNOTFREE

TRAF-5-MISMATCHCKSM

TRAF-5-DECREFCNTFAIL

TRAF-5-DECREMENTERR

TRAF-5-INVTRFIDX

TRAF-5-ALLOCFAIL

TRAF-5-INSERTFAIL

TRAF-5-NEWBLKALLOCFAIL

TRAF-5-BUFALLOCFAIL

TRAF-7-NOTENGBUF

TRAF-7-CONGOFF

DDTS "unknown"

VCM-5-WARNING

VCM-7-INFO

VCM-6-NOTICE

VCM-7-CONN_INSTALLSVC

CM-7-CONN_ALLOCVXL_E

DDTS "unknown"

VCM-7-VCM_INSTALL_XCO

VCM-7-VCM_BIG_DELETE_

VCM-7-VCM_RECOMMIT_TI

VCM-7-VCM_FRCE_RESYNC

VCM-6-NOTICE

DDTS "unknown"

CSR-7-INFO

CSR-6-NOTICE

CSR-5-WARNING

CSR-4-ERROR

CSR-7-CONGEST

CSR-7-NULL_PTR

CSR-7-MALLOC_FAIL

CSR-7-TIMEOUT

CSR-7-ABORT_FAIL

CSR-7-INTF

CSR-7-PEP

CSR-7-DISK_FAIL

CSR-7-START_END

CSR-7-BUFFER_UPDT

CSR-7-REDO_UPDT

DDTS "spvc"

SPVC-4-SWERROR

DDTS "axsm-apps/shm"

AXDG-4-ERR

AXDG-4-LOGTRC

AXDG-7-OFFLN

AXDG-7-ONLN_STATUS

DDTS "boot/shm"

BOOT-5-SERIALHUNGHCR

BOOT-5-SERIALHUNGREAD

BOOT-5-SERIALHUNGWRITE

BOOT-5-ETHERCHIPHUNG

BOOT-2-LANLOSTCARR

BOOT-2-LANLOSTCARR_CLR

BOOT-4-HMASTER_NO_HREA

BOOT-5-UNEXPECTED_INTE

BOOT-4-UNEXPECTED_INTE

BOOT-7-BURNBOOT_REQ_DE

BOOT-4-BURNBOOT_SIGFIL

BOOT-4-BURNBOOT_SIGFIL

BOOT-4-BURNBOOT_SW_ID_

BOOT-4-BURNBOOT_VER_IN

BOOT-4-BURNBOOT_KEY_IN

BOOT-7-BURNBOOT_SIGFIL

BOOT-7-BURNBOOT_BRAM_C

BOOT-7-BURNBOOT_VERSIO

BOOT-7-BURNBOOT_KEY_MA

BOOT-4-BURNBOOT_FAILED

BOOT-2-BURNBOOT_FAILED

BOOT-7-BURNBOOT_REQ_HA

BOOT-4-W_RODATA

DDTS "atmsig"

CA-4-CA_IPC_ERROR

CA-4-CA_TIMER_START_

CA-4-CA_GENERIC_ERRO

CA-6-CA_GENERIC_NOTI

DDTS "alarms"

CAM-5-INVALIDINPUT

CAM-5-PARMOUTOFTRANGE

CAM-5-PARMINVALID

CAM-5-PARMINVLENGTH

CAM-5-FUNCFAIL_STKDUM

CAM-5-QUEUEFULL

DDTS "ccma"

DAL-4-DALERR

DAL-4-DALERR_STR

DDTS "snmp-ma"

CB_S-4-INVALIDINPUT

CB_S-4-PARMINVALID

CB_S-4-PARMINVLENGTH

CB_S-4-FUNCFAILSTK

CB_S-4-FUNCFAIL

CB_S-4-PARMOUTOFRANGE

CB_S-4-MALLOCFAILED

CB_S-4-OPENTRANSFAIL

CB_S-4-BINDTRANSFAIL

CB_S-4-RCVFRTRNSFAIL

CB_S-4-MSGSENDFAIL

CB_S-4-MSGRECVFAIL

CB_S-4-BADSRMSLOT

CB_S-4-BADCARDTYPE

CB_S-4-INVVARBIND

CB_S-4-SEMCREATEERR

CB_S-4-SEMTAKEERR

CB_S-4-SEMGIVEERR

CB_S-4-BUFTAKEERR

CB_S-4-FRMBUFTAKEERR

CB_S-7-TOOFEWVARBINDS

CB_S-7-NOTRAPS

CB_S-6-TRAPLOG_WRAP

CB_S-6-RPMPORTCLOSED

CB_S-4-RPMOPENPORT

CB_S-4-OPENPORT

CB_S-4-PROCESSDEQ

CB_S-4-CREATEWATCHEDQ

CB_S-4-CREATENAMEDPORT

CB_S-4-GETPAKMSGFAIL

CB_S-4-IPCSENDMSGFAIL

CB_S-4-MSG_TOO_SMALL

CB_S-4-SOIINITFAIL

CB_S-4-QUEUEINITFAIL

CB_S-5-MSG_DROPPED

CB_S-5-TRAP_DROPPED

CB_S-5-TRAPBADSTATE

CB_S-5-NONRTMTRAP

CB_S-4-UNKNOWNMSG

CB_S-4-CLONETRAPERR

CB_S-4-PROXYRATINITFAI

CB_S-4-PROXYRATMSGFAIL

CB_S-4-PROXYRATSTATEFA

CB_S-4-PROXYERRORMISC

CB_S-4-TRAPSENDFAIL

CB_S-6-TASK_ATTACH

DDTS "shm"

CBC-4-CBC_DRV_ERR1

CBC-4-CBC_DRV_ERR2

CBC-4-CBC_DRV_ERR3

CBC-4-CBC_DRV_ERR4

CBC-4-CBC_DRV_ERR

Error Messages for MGX and SES Release 4.0.00

---

These error messages (also called Events) are for MGX and SES, Release 4.0.00.

ACAR-2-SHLFINIT

SEVERITY: Major Alert

FORMAT: "MAJOR_ALERT ERROR: %s"

THROTTLING: No Throttling

EXPLANATION: "Task Initialization Error"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: "Collect dsplog, dsperr, dspdbinfo 7 3 information"

ACAR-2-SHLFINIT_ENDPT

SEVERITY: Major Alert

FORMAT: "MAJOR_ALERT ERROR: %s %d"

THROTTLING: One Tick

EXPLANATION: "Task Initialization Error"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: "Collect dsplog, dsperr information"

ACAR-2-DBINIT

SEVERITY: Major Alert

FORMAT: "Slot:%u Init Error: %s"

THROTTLING: No Throttling

EXPLANATION: "Slot Database Initialization Error"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: " Collect dsplog, dsperr, dspdbinfo <slot> 3 information"

DDTS "pxm-connmgm"

CM_L-7-CM_LMI_NO_ALM_C

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Alarm info was not changed since last cycle"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

CM_L-7-CM_LMI_INIT_SUC

SEVERITY: Information

FORMAT: "CmLmiInit Successful %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "CmLmiInit Successful"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

CM_L-4-CM_LMI_MEM_ERRO

SEVERITY: Error

FORMAT: "Memory allocation error, %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to allocate memory-connection/alarm resync will be interrupted."

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

CM_L-4-CM_LMI_ERR_GEN

SEVERITY: Error

FORMAT: "PIPC error on line %d rc %d errno %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "pipcSend error. Data will not be sent to LSM"

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

CM_L-5-CM_LMI_ERR_SLOT

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Failed to retreive slot info from pcPro"

RECOMMENDED ACTION: No action required

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 requireM_L-4-CM_LMI_ERR_SEND

SEVERITY: Error

FORMAT: "Send Message failed %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error calling ssiMsgSend - Data will not be sent to LSM - will retry

SEVERITY: Error

FORMAT: "Initialization failure %s"

FLAG: No Flag

THROTTLING: One Tick

CM_L-2-CM_LMI_ERR_PORT

SEVERITY: Major Alert

FORMAT: "MAJOR_ALERT ERROR %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Task Initailizeation error - system will not come up"

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

CM_L-4-CM_LMI_ERR_SEND

SEVERITY: Error

FORMAT: "Send Message failed: %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error calling ssiMsgSend - Data will not be sent to LSM - will retry next periodic cycle"

RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call

CM_L-4-CM_LMI_ERR_MSGQ

SEVERITY: Error

FORMAT: "Initialization failure: %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Fail to bind message queue - CmLmiTask will not be able to receive messages - No connection/alarm resync will be performed"

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

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

CM_L-5-CM_LMI_ERR_SET_

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Unknown timeout event"

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

REQUIRED INFO: No Required Info

CM_L-4-CM_LMI_ERR_SCHE

SEVERITY: Error

FORMAT: "%s %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Error Calling ssiScheduleTimeout - periodic conn/alarm resynch disabled"

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

CM_L-4-CM_LMI_CREATE_T

SEVERITY: Error

FORMAT: "Creating Synch Timer failure %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error Creating Synch Timer - periodic conn/alarm will not be initiated"

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

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

CM_L-5-CM_LMI_LSLOT_ER

SEVERITY: Warning

FORMAT: "Unable to get Lslot info line %d, logSlot %d, prim value %d sec value %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error trying to access LSLOT INFO"

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

CM_L-5-CM_LMI_PSLOT_ER

SEVERITY: Warning

FORMAT: "Unable to get Pslot Info line %d phySlot %d errno %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error trying to access PSLOT INFO"

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

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

1) dspcds/dspcd

2) dspver

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

4) dsplog -sl < redundant slot if configured>

5) dsperr for the above slots.

6) Save the core file if required

DDTS "pxm-connmgm"

ACAR-2-SHLFINIT

SEVERITY: Major Alert

FORMAT: "MAJOR_ALERT ERROR %s"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Task Initialization Error"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: "Collect dsplog, dsperr, dspdbinfo 7 3 information"

ACAR-2-SHLFINIT_ENDPT

SEVERITY: Major Alert

FORMAT: "MAJOR_ALERT ERROR %s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Task Initialization Error"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: "Collect dsplog, dsperr information"

ACAR-2-DBINIT

SEVERITY: Major Alert

FORMAT: "Slot%u Init Error %s"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "Slot Database Initialization Error"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: "Collect dsplog, dsperr, dspdbinfo <slot> 3 information"

ACAR-2-SMM_ERROR_GEN

SEVERITY: Major Alert

FORMAT: "Slot %d SM Error %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Service Module Configuration Upload/Download Error"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: "Collect dsplog, dsperr information"

ACAR-4-MSG_PROC_ERR

SEVERITY: Error

FORMAT: "Slot %d Msg Proc Error %s errno 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "General Message Processing Error"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: "Collect dsplog, dsperr information"

ACAR-4-CHK_ERR

SEVERITY: Error

FORMAT: "Slot %d Check failed for Argument %s = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Check Failed for logged parameters"

RECOMMENDED ACTION: Indicates an internal error detected by the PXM connection management module. It needs to be analyzed by TAC and possibly by the development team.

REQUIRED INFO: "Collect dsplog, dsperr information"

ACAR-7-INFO_LOG

SEVERITY: Information

FORMAT: "Information Log %s Slot %d Card Type %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Informational Log"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "shm"

RED-7-DETECT_MISMATCH

SEVERITY: Information

FORMAT: "Detect mismatch: slot %d, version = %d, redType = %d, cd_type = %d (%d), redFeature = %d (%d)"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Detect mismatch on slot from tRed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-7-MSG_DATA_ERROR

SEVERITY: Information

FORMAT: "msg data err %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Message error. Data Errors and Unknown Msgs."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_SEND_MSG_ERR

SEVERITY: Information

FORMAT: "Could not send MSG to SM %s, slot %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Auto Card send message failed error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_GEN_ERR

SEVERITY: Information

FORMAT: "General ERROR %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Auto Card PMM related failure / Bram related failure. "

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-4-NACK_ERR

SEVERITY: Error

FORMAT: "%s %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Received a NACK from the SM. SM will be put to FAILED 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: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RED-7-AC_INFO_ERR

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Informational Event"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-TBL_UPD_INFO

SEVERITY: Information

FORMAT: "tRed INFO In %s at %u, %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed is updating redTable (lsmRedDb in SHM)."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_SWITCHCARD_I

SEVERITY: Information

FORMAT: "Info, %s, From Slot=%d, To Slot = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Autocard switch card event."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_MEM_ERR

SEVERITY: Information

FORMAT: "Memory error in system %s"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Auto Card memory error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_TIME_OUT_ERR

SEVERITY: Information

FORMAT: "State Time out %s"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "Auto Card time out error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_WRNGMSG_ERR

SEVERITY: Information

FORMAT: "ACRED Wrong msg rcvd %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Auto Card wrong message type error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_DWNLBRAMERR

SEVERITY: Information

FORMAT: "ACRED Download BRAM Failed %s"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "BRAM download error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_UPLDBRAMERR

SEVERITY: Information

FORMAT: "ACRED Upload BRAM Failed %s , slot %d"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "BRAM upload error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-BADARCERR

SEVERITY: Information

FORMAT: "%s BAD Archive from slot %d."

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "SM received a Bad configuration file."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-SMM_ERROR_GEN

SEVERITY: Information

FORMAT: "General Error %s"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: "General system error."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-SMM_INFO

SEVERITY: Information

FORMAT: "System Information %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "System Information."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-SMM_GEN_ERR

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "System Information."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-BAD_SHLF_SLOT

SEVERITY: Information

FORMAT: "Bad shelf slot num %s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "SMM bad shelf slot."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-RAM_SYNC_IOV_FA

SEVERITY: Information

FORMAT: "Call to %s returned error, ramDbId=0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed Ram Sync message create and sending errors"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-7-RAM_SYNC_IOV_SE

SEVERITY: Information

FORMAT: "Call to %s returned error, errno = %d, %s 0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed Ram Sync message send failed due to errrno"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-4-MSGQ_BIND_FAIL

SEVERITY: Error

FORMAT: "ssiMsgQBind FAILED"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "tRed task could not Bind to the Message Queue. This could cause tRed to not be able to receive any messages"

RECOMMENDED ACTION: "Collect information specified in REQUIRED_INFO field and call TAC"

REQUIRED INFO: "Collect hot core dump, event logs and errors"

RED-4-IPC_COM_EPID_FA

SEVERITY: Error

FORMAT: "%s returned %d, errno %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "tRed task could not create IPC Comm epid. Due to this tRed will not be able to receive or send IPC messages."

RECOMMENDED ACTION: "Collect information specified in REQUIRED_INFO field and call TAC"

REQUIRED INFO: "Collect hot core dump, event logs and errors"

RED-4-PIPC_PORT_CREAT

SEVERITY: Error

FORMAT: "pipcPortCreate Failed , return code = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed task could not create pipc port. Due to this tRed will not be able to send of received pipc messages"

RECOMMENDED ACTION: "Collect information mentioned in REQUIRE_INFO feild and call TAC"

REQUIRED INFO: "Collect hot core dump, event logs and errors"

RED-4-INIT_TBL_FAILED

SEVERITY: Error

FORMAT: "%s Failed to initialize "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "tRed task could not Initialize its database"

RECOMMENDED ACTION: "Collect the info in the REQUIRED_INFO field and call TAC"

REQUIRED INFO: "Collect a hot core dump, the event logs and err logs"

RED-7-SM_MSG_RCVD

SEVERITY: Information

FORMAT: "Received event %s from slot %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed received an event from the SM"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-6-AC_INCORRECT_ST

SEVERITY: Notice

FORMAT: "Slot %d, Current state %d, expected state %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed cannot process event as the expected state is different than the actual state"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-6-AC_INVALID_MSG

SEVERITY: Notice

FORMAT: "Slot %d, Msg type %x, srcId %d "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invalid message obtained by tRed "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-4-DOWNLOAD_FAILED

SEVERITY: Error

FORMAT: "Slot %d, %s returned %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed was not able to download the image to the sm "

RECOMMENDED ACTION: "Collect the info mentioned in REQUIRED_INFO and observe the card state"

REQUIRED INFO: "Collect the logs and error"

RED-7-DOWNLOAD_PASSED

SEVERITY: Information

FORMAT: "Slot %d, Download passed "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed was able to download the image to the sm "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-7-PMM_MSG_RCVD

SEVERITY: Information

FORMAT: "Received event %s from slot %d cardState = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed received a PMM event "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-4-CD_STATE_MISMAT

SEVERITY: Error

FORMAT: "Slot %d,cd state set to Mismatch.%s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "tRed card state changed to mismatch. The card will now be in the mismatch state"

RECOMMENDED ACTION: "Collect the logs and check the reason for mismatch and call TAC"

REQUIRED INFO: "Collect the dsplog and dsperr output"

RED-7-PMM_EVENT_SET

SEVERITY: Information

FORMAT: "PMM event %d set for slot %d, card state = %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "PMM event is set based on the card state by tRed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-7-SM_STATE_EVENT

SEVERITY: Information

FORMAT: "PMM event %d set for slot %d, card state = %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "PMM event is set based on the card state by tRed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-SM_STATE_CHANGE

SEVERITY: Warning

FORMAT: "pSlot = %d, Current State = %d, Event received =%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SM state is changed based on the event received"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-7-SM_INVALID_EVEN

SEVERITY: Information

FORMAT: "Invalid event %d received,pSlot = %d,State = %d,"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid event received by tRed for the current SM state"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-SEND_MISMATCH_M

SEVERITY: Warning

FORMAT: "%s. slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Send mismatch message to the slot from tRed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-IPC_MSG_RVC_ERR

SEVERITY: Warning

FORMAT: "IPC message receive error, errno = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error is receiving IPC message"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-SSI_RCVID_ERROR

SEVERITY: Warning

FORMAT: "ssi rcvid is NULL"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "ssi receive ID is Null"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-IPC_MSG_ALLOC_F

SEVERITY: Warning

FORMAT: "ssi ipc message allocation failed"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "ssi ipc message allocation failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-IPC_MSG_REPLY_F

SEVERITY: Warning

FORMAT: "ssi ipc message reply failed, errno = %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "failed to obtain the message reply throug ipc"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-CLI_INVALID_PAR

SEVERITY: Warning

FORMAT: "%s invalid command type %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameters passed to the tRed cli api"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-CLI_NULL_PARAM

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid parameters passed to the tRed cli api"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-IPC_MSG_SEND_FA

SEVERITY: Warning

FORMAT: "ipc message send failed, errno = %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "the ipc message send api returned and error and thus the message was not sent across to the recipient"

RECOMMENDED ACTION: "Collect the info mentioned in the REQUIRED_INFO field"

REQUIRED INFO: "Collect the hot core dump, the dsplog output and the dsperr output."

RED-5-IPC_DATAPTR_NUL

SEVERITY: Warning

FORMAT: "%d, Null data pointer received from ssi"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Null data pointer was recevied by the task from ssi"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-4-RED_CMD_MISMATC

SEVERITY: Error

FORMAT: "%s expected %d, received %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "mismatch between the expected command response and the command response actually received"

RECOMMENDED ACTION: "Collect the info mentioned in REQUIRED_INFO and call TAC"

REQUIRED INFO: "Collect the dsplog and dsperr outputs"

RED-7-INV_CLI_CMD

SEVERITY: Information

FORMAT: "Invalid command type received %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid command type received by tRed from cli"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-FW_UPGD_FAIL

SEVERITY: Warning

FORMAT: "%s slot %d, link state %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Firware upgrade failed for the slot as the slot was in redundancy and not meeting the loadrev criteria"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-5-CTC_INV_EVENT

SEVERITY: Warning

FORMAT: "Invalid CTC event received %d by tRed"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid CTC event received by tRed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

RED-4-CD_REMOVED

SEVERITY: Error

FORMAT: "card in slot %d removed , state = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed recevied an event that card is removed"

RECOMMENDED ACTION: "No action required. This event flags a removal of a card in the slot."

REQUIRED INFO: No Required Info

RED-4-CD_FAILED

SEVERITY: Error

FORMAT: "card in slot %d failed , state = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed recevied an event that card has failed"

RECOMMENDED ACTION: "Collect the info mentioned in REQUIRED_INFO and call TAC"

REQUIRED INFO: "Collect the hot core dump, the dsplog output and the dsperr output."

RED-7-AC_ADDRED_INFO

SEVERITY: Information

FORMAT: " %s, Pri Slot=%d,Sec Slot = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "addred event information"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_DELRED_INFO

SEVERITY: Information

FORMAT: " %s, Pri Slot=%d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "delred event information"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-CD_STATE_INFO

SEVERITY: Information

FORMAT: " %s, Slot=%d, state = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed card state set"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-PRIMARY_NOT_PRO

SEVERITY: Information

FORMAT: " %s,primSlot=%d, secSlot = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Primary slot not protected by secondary slot"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-SEC_CD_INFO

SEVERITY: Information

FORMAT: " %s, red type =%d, state = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Setting the Secondary card state"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-LINEMODULE_INFO

SEVERITY: Information

FORMAT: " %s,Slot %d,linemodule type=%d,red type = %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Line modules info logged byt tRed"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_MIB_MISMATCH

SEVERITY: Information

FORMAT: " MIB mismatch detected. state = %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "MIB mismatch detected by autocard"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-DWLD_INFO

SEVERITY: Information

FORMAT: "%s slot %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed download task info"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-5-DWLD_FOPEN_FAIL

SEVERITY: Warning

FORMAT: "%s slot %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "tRed download task file open failed"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-4-DWLD_FAILED

SEVERITY: Error

FORMAT: "%s slot %d, download type %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed download task failed for the slot. The card will be reset."

RECOMMENDED ACTION: "Collect information mentioned in the REQUIRED_INFO field and call TAC."

REQUIRED INFO: "Collect the dsplog and dsperr outputs."

RED-4-AC_INIT_FAIL

SEVERITY: Error

FORMAT: "%s, err %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "The Initialization of the tRed task failed due to tthe displayed error"

RECOMMENDED ACTION: "Collect the information mentioned in REQUIRED_INFO and call TAC"

REQUIRED INFO: "Collect a hot core dump, the dsplog output and the dsperr output."

RED-5-AC_INIT_ERR

SEVERITY: Warning

FORMAT: "%s, err %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "The Initialization of the tRed task had an error due to tthe displayed warning"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-AC_INIT_INFO

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Information regarding tRed Initialization"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-REDUNDANCY_INFO

SEVERITY: Information

FORMAT: "%s, slot %d "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Information regarding tRed redundancy"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-4-PMM_CD_RESET

SEVERITY: Error

FORMAT: "reseting slot %d, err %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "tRed is reseting the service module"

RECOMMENDED ACTION: "No action required. This event is logged when tREd resets a card."

REQUIRED INFO: No Required Info

RED-5-SM_INSERT_MSG

SEVERITY: Warning

FORMAT: "SM insertion message received. slot %d, state %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SM insertion message received by tRed for the slot"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-4-SM_FAILED_MSG

SEVERITY: Error

FORMAT: "SM failed message received. slot %d, state %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SM failed message received by tRed for the slot"

RECOMMENDED ACTION: "Collect the information mentioned in the REQUIRED_INFO field and call TAC"

REQUIRED INFO: "Collect the hot core dump, the dsplog output and the dsperr output."

RED-4-SM_MISMATCH_MSG

SEVERITY: Error

FORMAT: "SM mismatch message received. slot %d, state %d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "SM mismatch message received by tRed for the slot"

RECOMMENDED ACTION: "Collect the information mentioned in the REQUIRED_INFO field and call TAC."

REQUIRED INFO: "Collect the hot core dump, the dsplog output and the dsperr output."

RED-4-SM_REMOVED_MSG

SEVERITY: Error

FORMAT: "SM removed message received. slot %d, state %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SM removed message received by tRed for the slot"

RECOMMENDED ACTION: "No action required."

REQUIRED INFO: No Required Info

RED-7-CARD_FAIL_INFO

SEVERITY: Information

FORMAT: "%s%d"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Primary or Secondary Card Failed"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

RED-7-SHM_MSGRCV

SEVERITY: Information

FORMAT: "%s %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Message received by tRed from the SHM"

RECOMMENDED ACTION: "No action required."

REQUIRED INFO: No Required Info

RED-7-CMD_FAILED

SEVERITY: Information

FORMAT: "%s %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "tRed command failed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "alarms"

CAMA-5-INVALIDINPUT

SEVERITY: Warning

FORMAT: "One of the inputs to the function %s() was invalid."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for one of the parameters passed in as an argument to the named function was invalid."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAMA-5-PARMOUTOFTRANGE

SEVERITY: Warning

FORMAT: "Parm %s is out of range. The range is between %d and %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for the named parameter is out of range."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAMA-5-PARMINVALID

SEVERITY: Warning

FORMAT: "Parm %s value '0x%x' is invalid to %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAMA-5-PARMINVLENGTH

SEVERITY: Warning

FORMAT: "Parm %s invalid length of %d to %s. Max=%d Value='%s'"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The named paramater passed in as an argument to the named function either had a length of zero or exceeded the maximum value specified."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAMA-5-FUNCFAIL_STKDUM

SEVERITY: Warning

FORMAT: "%s() SNMP subsystem call to %s() failed. rc=%d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The specified function call failed. It failed with the specified return code. A stack trace was generated."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAMA-5-QUEUEFULL

SEVERITY: Warning

FORMAT: "Could not send Alarm Summary %d from slotnum %d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The CAM Client Queue has reached the high water mark"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "unknown"

AUPL-5-INVD_INPT

SEVERITY: Warning

FORMAT: "%s %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid input obtained from the NMS station. For example error could be due to invalid slot number specified, etc"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

AUPL-4-INVD_RET

SEVERITY: Error

FORMAT: "%s %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invalid Return code obtained from the APIs involved in transporting the file (eg due to response failure from SM etc)"

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

REQUIRED INFO: "Please collect the output of CLIs dspver, dspcds, dsplog, dsperr"

AUPL-4-INVD_VAL

SEVERITY: Error

FORMAT: "%s %s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid value computed eg for the ftp handler This could indicate a memory corruption in some cases"

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

REQUIRED INFO: "Please collect the output of CLIs dspver, dspcds, dsplog"

AUPL-4-INVD_STR

SEVERITY: Error

FORMAT: "%s %s %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid string obtained as input from the NMS station. For example error could be due to invalid filename specified, etc"

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

REQUIRED INFO: "Please collect the output of CLIs dspver, dspcds, dsplog"

AUPL-4-INVD_INPT

SEVERITY: Error

FORMAT: "%s %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid input obtained from the NMS station. For example error could be due to invalid slot number specified, etc"

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

REQUIRED INFO: "Please collect the output of CLIs dspver, dspcds, dsplog"

AUPL-4-INVD_RET

SEVERITY: Error

FORMAT: "%s %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invalid return code obtained from the APIs eg APIs involved in installing the pseudo-driver"

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

REQUIRED INFO: "Please collect the output of CLIs dspver, dspcds, dsplog, dsperr"

AUPL-4-INVD_VAL

SEVERITY: Error

FORMAT: "%s %s %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Invalid value computed eg flag for driver installation This could indicate a memory corruption in some cases"

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

REQUIRED INFO: "Please collect the output of CLIs dspver, dspcds, dsplog"

AUPL-4-INCRT_CALL

SEVERITY: Error

FORMAT: "%s %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Incorrect action by NMS stations eg attempt to write to a file etc"

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

REQUIRED INFO: "Please collect the output of CLIs dspver, dspcds, dsplog"

DDTS "axsm_apps"

APS-4-APS_MAIN_ERR

SEVERITY: Error

FORMAT: "APS Error Work Line index %s function 0X%X line %d exit due to major %d minor %d error"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Indicates an internal error detected by APS application in the main module. It needs to be analyzed by TAC and possibly by the APS development team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-4-APS_MUX_ERR

SEVERITY: Error

FORMAT: "APS Error Work Line index %s function 0X%X line %d exit due to major %d minor %d error"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This error indicates failure to update the APS backcard mux register. This could lead to incorrect behaviour of the APS line pair. It needs to be further analyzed by TAC and possibly by development team. In normal operation, such an error should never get reported."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-INIT_ERR

SEVERITY: Error

FORMAT: "APS Error Work Line index %s function 0X%X line %d exit due to major %d minor %d error"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This error indicates failure to create a task during the task initialisation sequence. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported"

RECOMMENDED ACTION: "Contact SSI team, review SSI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_MSG_ERR

SEVERITY: Error

FORMAT: "APS Error Slot Num %d function 0X%X line %d exit due to major %d minor %d error"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This error indicates failure to initialise message handler. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported"

RECOMMENDED ACTION: "Contact SSI team, review SSI eventlog to see failure reason."

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_IPC_COMEP_C

SEVERITY: Error

FORMAT: "APS ErrorCard %d function 0X%X line %d IPC com endpoint create failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This corresponds to ssiIpcComEpUnbind failure. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact SSI team, review SSI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_IPC_COMEP_U

SEVERITY: Error

FORMAT: "APS ErrorCard %d function 0X%X line %d IPC ComEp unbind send failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This correspnods to ssiIpcComEpUnbind failure. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact SSI team, review SSI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_IPC_COMEP_N

SEVERITY: Error

FORMAT: "APS ErrorCard %d function 0X%X line %d IPC ComEp namebind send failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This corresponds to ssiIpcComEpNameBind failure. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact SSI team, review SSI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_IPC_MSG_SEN

SEVERITY: Error

FORMAT: "APS ErrorCard %d function 0X%X line %d IPC Msg send failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This corresponds to ssiIpcMessageSend failure. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact SSI team, review SSI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_IPC_MSG_ALL

SEVERITY: Error

FORMAT: "APS ErrorCard %d function 0X%X line %d IPC Msg alloc failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS could not allocated memory for a message. This could lead to incorrect behaviour of APS module. It needs to be further analysed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact SSI team, review SSI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_EM_REPORT_F

SEVERITY: Error

FORMAT: "APS ErrorCard %d function 0X%X line %d EM Root report failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "EM could not be informed of EMROOT_INIT_DONE. emRootReportDone failed"

RECOMMENDED ACTION: "Contact SSI team to review send failure reason."

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_MSG_HNDLR_I

SEVERITY: Error

FORMAT: "APS ErrorCard %d function 0X%X line %d Msg Handler init failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Card Task Msg handler init Failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact SSI team, review SSI eventlog to see failure reason."

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_SEND_FA

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI send purge failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Corresponds to ssiRmiRmtEpidCtxtPurge failure. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from RMI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact RMI team, review RMI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_CTXT_PU

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMIctxt purge failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Corresponds to ssiRmiRmtEpidCtxtPurge failure. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from RMI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact RMI team, review RMI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_USER_AC

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI user ack data send failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ssiRmiUsrAckedDataAck send failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from RMI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact RMI team, review RMI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_ACKDATA

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI ack data send failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ssiRmiAckedDataSendAndReset failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from RMI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact RMI team, review RMI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_MSG_ALL

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI Msg Alloc failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ssiRmiMsgAllocate failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from RMI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact RMI team, review RMI eventlog to see failure reason. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_INVALID_CAR

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d Invalid Card Event major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Invalid Card Event message recived by APS task. PHY task has reported a card event which is neither UP nor DOWN. Please check the eventlog for error type. In normal operation, such an error should never get reported."

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

REQUIRED INFO: "Capture the output of following shell command on Active AXSM card.

a) ApsDisplayEventTraceLineId 0,0,0 "

APS-4-APS_RMI_LINE_PA

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI line pair cntxt sync failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Context Sync to line pair failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_UNACK_D

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI unack data send failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ssiRmiUnackedDataSend failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_SYNC_DA

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI sync data send failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ssiRmiSyncDataSend failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from SSI team. In normal operation, such an error should never get reported."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_RMT_EPI

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI remote epid create failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ssiRmiRmtEpidCtxtCreate failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from RMI team. In normal operation, such an error should never get reported."

RECOMMENDED ACTION: "Contact RMI team, review RMI eventlog to see failure reason."

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_UNKNOWN_MSG

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d Unknwon Message recd. major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Unknown message reveived by APS card task for relaying to the peer card."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-4-RMI_UNACK_DATAS

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI unAckdata send failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ssiRmiUnackedDataSend failed. This could lead to incorrect behaviour of APS module. It needs to be further analyzed by TAC and possibly from RMI team. In normal operation, such an error should never get reported."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_RMI_PORT_CR

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d RMI port create failed major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "ssiRmiPortCreate failed ie. APS task failed to create inter-card RMI port for communication. This would cause no communication between Active and Standby card. It needs to be further analyzed by TAC and possibly from RMI team. In normal operation, such an error should never get reported."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-APS_INVALID_EPI

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d Invalid EPID major %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Invalid EPID. IPC endpoint-id is not initialised."

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 information required. "

APS-4-APS_INVALID_CTC

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d Invalid CTC card role %d minor %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Invalid CTC card role. Card role is neither ACTIVE nor STAND-BY. "

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

REQUIRED INFO: "Capture the output of following CLI commands On PXM45

a) dspcd <slot-id of the PRIMARY AXSM card>

b) dspcd <slot-id of the SECONDARY AXSM card if redundancy configured> "

APS-4-APS_RMT_BKCD_DE

SEVERITY: Error

FORMAT: "APS Error Card index %s function 0X%X line %d Back Card presence detect failed %d %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Back card or mini back plane not installed properly"

RECOMMENDED ACTION: "Remove and reinsert the backcards / minibackplane"

REQUIRED INFO: "Capture the output of 'dspapsbkplane' on ACTIVE and STANDBY card"

APS-4-APS_RMT_FRONTCD

SEVERITY: Error

FORMAT: "APS Error Card %d function 0X%X line %d Remote Front card presence detect failed Check Front Cd/MiniBackplane %d %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Back card or mini back plane not installed properly"

RECOMMENDED ACTION: "Remove and reinsert the backcards / minibackplane"

REQUIRED INFO: "Capture the output of 'dspapsbkplane' on ACTIVE and STANDBY card"

APS-4-APS_INVALID_CTC

SEVERITY: Error

FORMAT: "APS Error Card index %d function 0X%X line %d Invalid CTC cd role %d %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "LinePairTask detected invalide CTC Card role. Card role is neither ACTIVE nor STAND-BY."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of following CLI commands On PXM45

a) dspcd <slot-id of the PRIMARY AXSM card>

b) dspcd <slot-id of the SECONDARY AXSM card if redundancy configured> "

APS-7-APS_AISL_DECL

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d AISL exists on Line index%s CHMM/PSBF not detected or cleared TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "AISL exists. Channel Mismatch/PSBF will not be processed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PRDI

SEVERITY: Information

FORMAT: "APS Event Work Line index %s P_RDI is %s for both the lines "

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Enable/Disable P_RDI generation"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_SF_DECL

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d SF declared TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SF declared on the line"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_SELECTOR_RE

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d Selector Released TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS selector state released"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PROT_LINE_S

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d Protection LineSelected State TXK1K2RXK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS selector state protection line selected"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_BRIDGE_RELE

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d Bridge Released State TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS bridge state released"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_WORKCHAN_BR

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d Working Channel Bridged State TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS working channel bridged"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_TXK1

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d TxK1 set TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS TXK1 set to a new value"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_TXK2

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d TxK2 set TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS TXK2 set to a new value"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_RXK1

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d RxK1 changed TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS RXK1 changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_RXK2

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d RxK2 changed TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS RXK2 changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PROVISION

SEVERITY: Information

FORMAT: "APS Event Work Line %s function 0X%X line %d APS line pair provisioned. Protection Line %s Architecture %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS line pair is provisioned"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_DELETE

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d APS line pair deleted. Prot Line index %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS line pair is deleted"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_CONFIG_SF_B

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d config changeSF BER changed from 1E-%d to 1E-%d "

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS SF BER configuration changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_CONFIG_SD_B

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d config changeSD BER changed from 1E-%d to 1E-%d "

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS SD BER configuration changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_CONFIG_WTR

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d config changeWTR changed from %d to %d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS WTR value changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_CONFIG_DIR

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d config direction changed to %s, TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS line pair mode, direction changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_CONFIG_REV

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d APS line pair config mode changed to %s, TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS line pair revertive/non-revertive config changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_USER_SWITCH

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d user switch request switchOption %d service switch %d\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS user switch request. Could be Clear, Forced or Manual switch Working to Protection, Forced or Manual switch protection to working, service switch"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PSB_INVALCH

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d PSB invalid channel TXK1K2RxK1K2 0x%x minor 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Protection Switching Byte defect was detected due to an invalid channel."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PSB_INVALCO

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d PSB invalid code TXK1K2RxK1K2 0x%x minor 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Protection Switching Byte defect was detected due to an unused code."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PSB_INCONSB

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d PSB inconsistent Byte TXK1K2RxK1K2 0x%x minor 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Protection Switching Byte defect was detected due to an Inconsistent byte in the recd. K1."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PSB_IRRELEV

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d PSB irrelevant request TXK1K2RxK1K2 0x%x minor 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Protection Switching Byte defect was detected due to an Irrelevant request in the recd. K1."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PSB_FAILURE

SEVERITY: Information

FORMAT: "APS Event Work Line index %s function 0X%X line %d PSBF declared TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Protection Switching Byte Failue declared"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_PSBF_CLEARE

SEVERITY: Information

FORMAT: "APS Error Work Line index %s function 0X%X line %d PSBF is cleared TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "PSBF has been Cleared"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_CHMM_CLEARE

SEVERITY: Information

FORMAT: "APS Error Work Line index %s function 0X%X line %d Channel Missmatch cleared TXRXK1K2 0x%x "

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Channel mismatch Failure Cleared."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-6-ADD_LN

SEVERITY: Notice

FORMAT: "APS Line Redundancy added with Work Line = %d.%d.%d, Prot Line = %d.%d.%d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Added. The event log would show the working and protection line indices. "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-6-DEL_LN

SEVERITY: Notice

FORMAT: "APS Line Redundancy deleted with Work Line = %d.%d.%d , Prot Line = %d.%d.%d"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Pair deleted. The event log would show working and protection line indices."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-3-SW_CLEAR

SEVERITY: Minor Alert

FORMAT: "User Requested APS Clear successful workLN %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Clear Switch happened due to User Initiated Request. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-3-SW_LOCK

SEVERITY: Minor Alert

FORMAT: "User Requested APS Lockout successful workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Lockout happened due to User Initiated Request. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-3-SW_FORCE_WTOP

SEVERITY: Minor Alert

FORMAT: "User Requested APS Forced Work->Prot successful workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Forced W->P Switch happened due to User Initiated Request. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-3-SW_FORCE_PTOW

SEVERITY: Minor Alert

FORMAT: "User Requested APS Forced Prot->Work successful workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Forced P->W Switch happened due to User Initiated Request. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-3-SW_MAN_WTOP

SEVERITY: Minor Alert

FORMAT: "User Requested APS Manual Work->Prot successful workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Manual W->P Switch happened due to User Initiated Request. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-3-SW_MAN_PTOW

SEVERITY: Minor Alert

FORMAT: "User Requested APS Manual Prot->Work successful workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Manual P->W Switch happened due to User Initiated Request. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-2-PSB_FAIL

SEVERITY: Major Alert

FORMAT: "APS Protection Switch Byte Failure workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Protection Switching Byte Failure occured."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsplog -sl <other slot in the pair if redundancy is configured> -mod APS

On each AXSM card, at both ends of the APS line

a) dspver

b) dspapsbkplane - for intercard APS setup only. Capture output

on Active and Standby cards.

c) dspapsln <the line mentioned in the eventlog>

d) dspalm -sonet <line mentioned in the eventlog>

e) dspbecnt <line mentioned in the eventlog>

Capture the output of following shell command on Active and Standby AXSM cards ApsDisplayEventTraceLineId <slot-id> <0-based baynum>

APS-2-CHAN_MISMATCH

SEVERITY: Major Alert

FORMAT: "APS Channel Mismatch workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Channel Mismatch Failure occured. Channel-id received in RxK2 is different than the channel-id in TxK1"

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsplog -sl <other slot in the pair if redundancy is configured> -mod APS

On each AXSM card, at both ends of the APS line

a) dspver

b) dspapsbkplane - for intercard APS setup only. Capture output

on Active and Standby cards.

c) dspapsln <the line mentioned in the eventlog>

d) dspalm -sonet <line mentioned in the eventlog>

e) dspbecnt <line mentioned in the eventlog>

Capture the output of following shell command on Active and Standby AXSM cards ApsDisplayEventTraceLineId <slot-id> <0-based baynum>

APS-2-PRIM_SEC_MISMAT

SEVERITY: Major Alert

FORMAT: "APS Primary Section Mismatch workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Primary Section Mismatch Failure occured. Section-id received in RxK2 is different than the Section-id in TxK2"

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsplog -sl <other slot in the pair if redundancy is configured> -mod APS

On each AXSM card, at both ends of the APS line

a) dspver

b) dspapsbkplane - for intercard APS setup only. Capture output

on Active and Standby cards.

c) dspapsln <the line mentioned in the eventlog>

d) dspalm -sonet <line mentioned in the eventlog>

e) dspbecnt <line mentioned in the eventlog>

Capture the output of following shell command on Active and Standby AXSM cards ApsDisplayEventTraceLineId <slot-id> <0-based baynum>

APS-6-CNF_SFBER

SEVERITY: Notice

FORMAT: "APS Line Reconfigured. SF BER changed from 1E-%d to 1E-%d workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SF Ber changed by user. The old and new SF Ber values will be displayed in the eventlog. "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-6-CNF_SDBER

SEVERITY: Notice

FORMAT: "APS Line Reconfigured. SD BER changed from 1E-%d to 1E-%d workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "SD Ber changed by user. The old and new SD Ber values will be displayed in the eventlog. "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-6-CNF_WTR

SEVERITY: Notice

FORMAT: "APS Line Reconfigured. WTR changed from %d to %d workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Wtr changed by user. The old and new WTR values will be displayed in the eventlog. "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-6-CNF_DIR

SEVERITY: Notice

FORMAT: "APS Line Reconfigured. Direction changed to %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "DIR changed by user. The event is logged only when there is change in the direction. New direction can be determined by event log."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-CNF_PROTO

SEVERITY: Information

FORMAT: "APS Line Reconfigured Protocol changed from %s to %s for workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS line pair mode, protocol changed"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-CNF_OPMODE

SEVERITY: Information

FORMAT: "Card configured for: %s "

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Card is configured either of AxsmA/AxsmB"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-7-APS_OPMODE_ERR

SEVERITY: Information

FORMAT: "ERROR card configured for %s software, PXM has returned NULL info for logical slot "

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "By default card is configured as AxsmA, PXM has sent NULL info for slot"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-6-CNF_REV

SEVERITY: Notice

FORMAT: "APS Line Reconfigured. Mode changed to %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "REV changed by user. The event is logged only when there is change in the mode. New value can be determined by the event log."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-3-SF_DECL

SEVERITY: Minor Alert

FORMAT: "APS SF Bit Error on Line Index = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Signal Fail condition detected."

RECOMMENDED ACTION: "Check the line cable on local end and remote end. Check the backcard status on local end and remote end. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsplog -sl <other slot in the pair if redundancy is configured> -mod APS

On each AXSM card, at both ends of the APS line

a) dspver

b) dspapsbkplane - for intercard APS setup only. Capture output

on Active and Standby cards.

c) dspapsln <the line mentioned in the eventlog>

d) dspalm -sonet <line mentioned in the eventlog>

e) dspbecnt <line mentioned in the eventlog>

Capture the output of following shell command on Active and Standby AXSM cards ApsDisplayEventTraceLineId <slot-id> <0-based baynum>

APS-3-SF_DECL_CLEAR

SEVERITY: Minor Alert

FORMAT: "APS SF Bit Error Cleared on Line Index = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Signal Fail alarm condition cleared. Logging the event for informational purpose."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

On AXSM card

a) dspver b)dspapsln <the line mentioned in the eventlog> "

APS-3-SW_SERVICE

SEVERITY: Minor Alert

FORMAT: "User Requested APS Service Switch workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Service Switch requested by user is successful. Traffic may have been disturbed."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-4-PSBF_CLEARED

SEVERITY: Error

FORMAT: "APS Protection Switch Byte Failure Cleared workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Protection Switching Byte Failure has been Cleared."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-4-CHAN_MIS_CLEARE

SEVERITY: Error

FORMAT: "APS Channel Mismatch Failure Cleared workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Channel mismatch Failure Cleared. RxK1 and TxK1 channel-ids matched."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-2-FAR_END_FAIL

SEVERITY: Major Alert

FORMAT: "APS Far End Failure workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Far end Protection Line Failure detected. "

RECOMMENDED ACTION: "Check the protection line status on the remote node. "

REQUIRED INFO: "Capture the output of following CLIs on both nodes. On PXM45

a) dsplog -sl <slot that experianced the error> -mod APS

On AXSM card

a) dspver b)dspapsln <the line mentioned in the eventlog> "

APS-2-FAR_END_FAIL_CL

SEVERITY: Major Alert

FORMAT: "APS Far End Failure cleared workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Far end Prot Byte Fail Cleared. This may result into line switch."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-2-MODE_MISMATCH

SEVERITY: Major Alert

FORMAT: "APS Mode Mismatch workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS mode mismatch detected. RxK2 byte mode is different from the Provisioned mode. This may result into change in the APS line operating mode. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

On AXSM card

a) dspver b)dspapsln <the line mentioned in the eventlog> "

APS-6-MODE_MIS_CLEAR

SEVERITY: Notice

FORMAT: "APS Mode Mismatch Cleared workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS mode mismatch cleared. RxK2 byte mode is same as the Provisioned mode. This may result into change in the APS line operating mode."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-4-SW_CLEAR_FAIL

SEVERITY: Error

FORMAT: "Cannot do APS Switch Clear %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Clear command Failed. Check the reason displayed in the eventlog."

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

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-4-SW_LOCK_FAIL

SEVERITY: Error

FORMAT: "Cannot do APS Switch Lockout %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Lockout command failed. Check the reason displayed in the eventlog."

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

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-4-SW_FORCE_WTOP_F

SEVERITY: Error

FORMAT: "Cannot do APS Switch Forced Work->Prot %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Forced W->P Switch command failed. Check the reason displayed in the eventlog"

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-4-SW_FORCE_PTOW_F

SEVERITY: Error

FORMAT: "Cannot do APS Switch Forced Prot->Work %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Forced P->W Switch command failed. Check the reason displayed in the eventlog"

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-4-SW_MAN_WTOP_FAI

SEVERITY: Error

FORMAT: "Cannot do APS Manual Switch Work->Prot %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Manual W->P Switch command failed. Check the reason displayed in the eventlog."

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

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-4-SW_MAN_PTOW_FAI

SEVERITY: Error

FORMAT: "Cannot do APS Manual Switch Prot->Work %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Manual P->W Switch command failed. Check the reason displayed in the eventlog."

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

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-3-SD

SEVERITY: Minor Alert

FORMAT: "APS Signal Degrade on Line Index %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line Signal Degrade alarm detected. "

RECOMMENDED ACTION: "Check the cable and backcard status."

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsplog -sl <other slot in the pair if redundancy is configured> -mod APS

On each AXSM card, at both ends of the APS line

a) dspver

b) dspapsbkplane - for intercard APS setup only. Capture output

on Active and Standby cards.

c) dspapsln <the line mentioned in the eventlog>

d) dspalm -sonet <line mentioned in the eventlog>

e) dspbecnt <line mentioned in the eventlog>

Capture the output of following shell command on Active and Standby AXSM cards ApsDisplayEventTraceLineId <slot-id> <0-based baynum>

APS-3-SD_CLEAR

SEVERITY: Minor Alert

FORMAT: "APS Signal Degrade Cleared on Line Index %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Line SD cleared. Logging the event for informational purpose."

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "No information required. "

APS-3-SW_SF

SEVERITY: Minor Alert

FORMAT: "APS Internal Switch due to APS Signal Fail High %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Switch due to Signal Fail. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

On AXSM card

a) dspver b)dspapsln <the line mentioned in the eventlog> "

APS-3-SW_SD

SEVERITY: Minor Alert

FORMAT: "APS Internal Switch due to APS Signal Degrade High %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Switch due to Signal Degrade. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

On AXSM card

a) dspver b)dspapsln <the line mentioned in the eventlog> "

APS-3-SW_REV

SEVERITY: Minor Alert

FORMAT: "APS Reverse Request switch %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Reverse Request Switch. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

On AXSM card

a) dspver b)dspapsln <the line mentioned in the eventlog> "

APS-3-SW_DONOT_REV

SEVERITY: Minor Alert

FORMAT: "APS Do Not Revert Request switch %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Do Not Revert Request Switch. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

On AXSM card

a) dspver b)dspapsln <the line mentioned in the eventlog> "

APS-3-SW_WTR

SEVERITY: Minor Alert

FORMAT: "APS Wait To Restore Expire switch %s workLN = %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "APS Switch on Wait To Restore timer expiration. "

RECOMMENDED ACTION: "No action required. "

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

On AXSM card

a) dspver b)dspapsln <the line mentioned in the eventlog> "

APS-3-SW_UNKNOWN

SEVERITY: Minor Alert

FORMAT: "APS Unknown switch Reason %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Unknown switch Reason. In normal operation, such an error should never get reported."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

APS-4-SW_SF_FAIL

SEVERITY: Error

FORMAT: "APS Internal Switch due to APS Signal Fail High FAILED %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Switch due to SF failed. "

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

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-4-SW_SD_FAIL

SEVERITY: Error

FORMAT: "APS Internal Switch due to APS Signal Degrade FAILED %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Switch due to SD failed. "

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

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-4-SW_REV_FAIL

SEVERITY: Error

FORMAT: "APS Reverse Request switch FAILED %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Reverse Request Switch Failed. "

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

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-3-SW_DONOT_REV_FA

SEVERITY: Minor Alert

FORMAT: "APS Do Not Revert Request switch Failed %s workLN = %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Do Not Revert Request Switch Failed. "

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

REQUIRED INFO: "Capture the output of these CLIs

a) dspver

b) dspapsln <the line mentioned in the eventlog>

Capture the output of following shell command on Active card ApsDisplayEventTraceLineId <slot-id> <0-based baynum> <0-based linenum> "

APS-7-APS_CHMM_FAILUR

SEVERITY: Information

FORMAT: "APS Error Work Line index %s function 0X%X line %d Channel Mismatch Failure declared TXK1K2RxK1K2 0x%x"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Channel Mismatch Failure declared. RxK1 and TxK1 channel-id do not match."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

APS-4-APS_PHY_ERR

SEVERITY: Error

FORMAT: "APS Error Line index %s function 0X%X line %d exit due to major %d minor %d error"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "APS Task Error in Phy api module. Unable to read/write register."

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

REQUIRED INFO: "No information required. "

APS-4-APS_PHY_BAD_PAR

SEVERITY: Error

FORMAT: "PHY Error function 0X%X, line %d passed invalid param to DRV_set LineObj 0x%x, chanDesc 0x%x, param_id %d"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "APS Task Error in Phy api module. DRV returned error due to bad input parameter."

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

REQUIRED INFO: "Capture the output of these CLIs On PXM45

a) dsplog -sl <slot that experianced the error>

b) dsperr -sl <slot that experianced the error> "

DDTS "unknown"

SSI-4-ARCH_ERROR

SEVERITY: Error

FORMAT: "Archive Error %s "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The archive file doesn't exist on the service module."

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

SSI-4-ARCH_ERROR

SEVERITY: Error

FORMAT: "Archive Error %s "

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The archive file for the corresponding service module could be either corrupted or failed to create."

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

REQUIRED INFO: "Collect dsplog, dsperr, dspdbinfo <slot> 3 information"

DDTS "shm"

ENVM-4-ADC_CONV_ERROR

SEVERITY: Error

FORMAT: "ADC Conversion Failed"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event indicates an error condition in the A/D Converter. Specifically, a sensor could not be monitored. We allow a total of three errors before logging this event."

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

REQUIRED INFO: " a) From shellconn on PXM pxm> lkup \"adcError\" Dump given memory location using \"d\"

b) dspenvalms on PXM

c) Fromm shellconn on PXM

pxm> showall(1) Capture debug output pxm> showall(0) "

ENVM-4-ADC_ERROR

SEVERITY: Error

FORMAT: "ADC Error"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event indicates an error condition in the A/D Converter. Specifically, a sensor could not be monitored. We allow a total of three errors before logging this event."

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

REQUIRED INFO: " a) From shellconn on PXM pxm> lkup \"adcError\" Dump given memory location using \"d\"

b) dspenvalms on PXM

c) Fromm shellconn on PXM

pxm> showall(1) Capture debug output pxm> showall(0) "

ENVM-2-ENV_ALARM_SET

SEVERITY: Major Alert

FORMAT: "Environmental Alarm Set %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event indicates an environmental monitoring alarm has occurred."

RECOMMENDED ACTION: No action required

REQUIRED INFO: " a) dsplog -mod ENVM on PXM

b) dspndalms on PXM

c) dspenvalms on PXM "

ENVM-3-ENV_ALARM_CLR

SEVERITY: Minor Alert

FORMAT: "Environmental Alarm Clr %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event indicates an environmental monitoring alarm has cleared."

RECOMMENDED ACTION: No action required

REQUIRED INFO: " a) dsplog -mod ENVM on PXM

b) dspndalms on PXM

c) dspenvalms on PXM "

ENVM-4-ENV_TRAP_GEN

SEVERITY: Error

FORMAT: "Cannot Send Trap %s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event indicates an error in sending an enviromental monitoring trap to the network management system(s)."

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

b) dspndalms on PXM

c) dspenvalms on PXM "

ENVM-4-ENV_ERROR

SEVERITY: Error

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "This log event indicates a failure in an API called by the environmental monitoring code."

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

REQUIRED INFO: " a) dsplog -mod ENVM on PXM

b) dspndalms on PXM

c) dspenvalms on PXM

d) from shellconn on PXM

pxm> showNode Capture output of debug display. "

DDTS "drivers/ccma"

ATLA-4-AT_INIT_ERR

SEVERITY: Error

FORMAT: "ATLAS Error Atlas No %d function 0X%X line %d exit due to %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " Error Caused during Initialisation of Atlas"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATLA-4-AT_INTRPT_ERR

SEVERITY: Error

FORMAT: "ATLAS Error Atlas No %d function 0X%X line %d exit due to %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " Specifies the Interrupts caused."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATLA-4-AT_GEN_ERR

SEVERITY: Error

FORMAT: "ATLAS Error Atlas No %d function 0X%X line %d exit due to %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " General Error. "

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATLA-4-AT_PARAM_ERR

SEVERITY: Error

FORMAT: "ATLAS Error Atlas No %d function 0X%X line %d exit due to %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " Incorrect parameter was passed to ATLAS driver."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATLA-4-AT_ACCESS_ERR

SEVERITY: Error

FORMAT: "ATLAS Error Atlas No %d function 0X%X line %d exit due to %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " Access to Atlas failed. ATLAS is busy. The major and minor params have been specified."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATLA-4-AT_CONACC_ERR

SEVERITY: Error

FORMAT: "ATLAS Error Atlas No %d function 0X%X line %d exit due to %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: " Access Connection information failed."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "atmsig"

ATMC-5-INTERNAL_CRITIC

SEVERITY: Warning

FORMAT: "%s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "It describes the internal error for Connection Management module on PNNI controller."

RECOMMENDED ACTION: "Gather the following information: connection statuschanged? Interface status changed? And then contact your TAC representative."

REQUIRED INFO: "Collect node info on PNNI controller using command of (dsplog), (dspcds), (dspver), (dsplog -mod ATMC), (dspconinfo)"

ATMC-5-P2MP_ERR

SEVERITY: Warning

FORMAT: "%s"

FLAG: Stack Trace

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATMC-5-P2MP_WARN

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATMC-7-P2MP_INFO

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATMS-4-ATMSIG_PRTY_INS

SEVERITY: Error

FORMAT: "ATMSIG(%s %d,%d - %04d/%02d) avl prty ins failedsvc 0x%x party 0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to store into SVC party database."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_PRTY_DEL

SEVERITY: Error

FORMAT: "ATMSIG(%s %d,%d - %04d/%02d) avl prty del failedsvc 0x%x party 0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to delete from SVC party database."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_SVC_INSE

SEVERITY: Error

FORMAT: "ATMSIG(%s %d,%d - %04d/%02d) SVC wavl ins failedsvc 0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to store into SVC connection database."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-ATMSIG_SVC_DELE

SEVERITY: Error

FORMAT: "ATMSIG(%s %d,%d - %04d/%02d) SVC wavl del failedsvc 0x%x"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to delete from SVC connection database."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-NOSVC

SEVERITY: Error

FORMAT: "no SVC, %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "No SVC datastructure found for connection."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-NOCALLREF

SEVERITY: Error

FORMAT: "Cannot find a Callref value to allocate %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "The call reference structures are inconsistant."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-6-FAILHALFLEGREM

SEVERITY: Notice

FORMAT: "halfLeg removal failed, %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to remove endpoint connection resources."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-FAIL2NDHALFLEG

SEVERITY: Error

FORMAT: "halfLeg removal failed, %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Failed to remove endpoint connection resources."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

ATMS-4-FAILXCONN

SEVERITY: Error

FORMAT: "Xconn failed, %s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Synchronous faliure in connection commit."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

SCHE-4-UNEXPECTEDMESSA

SEVERITY: Error

FORMAT: "Unknown message %x received (msgb %x, ssi_rcvid %x)."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Task cannot recognize the 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: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

SCHE-4-UNEXPECTEDEVENT

SEVERITY: Error

FORMAT: "Process received unknown event (maj %x, min %x)."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Unexpected event received in current 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: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

SCHE-4-UNEXPECTEDTIMER

SEVERITY: Error

FORMAT: "Unknown timer expiration, timer = %x, type %d."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Timeout received with invalid context."

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

REQUIRED INFO: On PXM cli the output of the following commands dspver, dspcds, dspdate, dsppnports, dspsigstats, dsppncons, dsppnctlvc, dsplog, dspmempart can be sent to the Cisco Customer support.

DDTS "unknown"

ADDR-5-ADDR_ERROR

SEVERITY: Warning

FORMAT: "%s"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ADDR-7-ADDR_INFORMATIV

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "ifm"

IFM-4-ERROR

SEVERITY: Error

FORMAT: "IFM Internal Err%s"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: "It describes the internal error for IFM module on PNNI controller."

RECOMMENDED ACTION: "Target which interface has problem and check(1)if the interface status has changed;(2)if there are connections on the interface and if connections status has changed or not.Gather all the interface related information and contact your TAC representative."

REQUIRED INFO: "Collect node info on PNNI controller using dspver,dspcds,dsppnports; collect IFM log using (dsplog -mod IFM);if specific port is known,collect port info using (dsppnport portID)"

IFM-5-CRITICAL

SEVERITY: Warning

FORMAT: "%s"

FLAG: Stack Trace

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFM-5-WARNING

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFM-7-INFO

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

IFM-6-NOTICE

SEVERITY: Notice

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "atmsig"

VCM-6-LEG_CREATE

SEVERITY: Notice

FORMAT: "PnNet/VCM/%s: %s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Information about control vc leg creation status"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATMC-5-INTERNAL_WARNIN

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATMC-5-SETCAC_WARN

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATMC-5-BITMAP_ERR

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATMC-5-BITMAP_WARN

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

ATMC-7-BITMAP_INFO

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "atmsig"

TRAF-5-ADDFAIL

SEVERITY: Warning

FORMAT: "%s Fail to add %s trf parm to database"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Fail to add traffic parameter to database"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-DELFAIL

SEVERITY: Warning

FORMAT: "%s Fail to del %s trf parm from database"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Fail to delete traffic parameter from database"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-NOABRPARM

SEVERITY: Warning

FORMAT: "%s Missing %s abr trf parm for abr conn"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Missing abr traffic parameters for abr conn"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-DBCREATEFAIL

SEVERITY: Warning

FORMAT: "%s Not able to create DB"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Not able to create DB"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-NULLPTR

SEVERITY: Warning

FORMAT: "%s %s is null at position %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Given pointer is null"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-NULLELEPTR

SEVERITY: Warning

FORMAT: "%s %s is null with index %d at position %d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Given element pointer is null"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-BADELE

SEVERITY: Warning

FORMAT: "%s Bad %s traffic element - index=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Bad element in traffic database"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-BADELECHKSUM

SEVERITY: Warning

FORMAT: "%s Bad %s trf ele in same chksum list - index=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Bad traffic element in same checksum list"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-BROKENLIST

SEVERITY: Warning

FORMAT: "%s Broken same chksum list for %s trf - index=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Broken link list"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-NOTINFREELIST

SEVERITY: Warning

FORMAT: "%s %s - index %d not in free list"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Element not in free list"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-NOTINUSE

SEVERITY: Warning

FORMAT: "%s %s - index %d not in use"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Element not in use"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-NOTALLOC

SEVERITY: Warning

FORMAT: "%s %s - index %d not allocated"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Element not allocated"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-CANNOTFREE

SEVERITY: Warning

FORMAT: "%s Ref count not equal to 1 for %s trf index=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Cannot free element because someone still refering to it"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-MISMATCHCKSM

SEVERITY: Warning

FORMAT: "%s %s trf chksum mismatch - index=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Traffic chksum mismatch"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-DECREFCNTFAIL

SEVERITY: Warning

FORMAT: "%s Decrease reference count fail - index=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Decrease reference count fail"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-DECREMENTERR

SEVERITY: Warning

FORMAT: "%s %s trf decrement error - total outstanding already zero "

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Decrement error total outstanding already zero"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-INVTRFIDX

SEVERITY: Warning

FORMAT: "%s %s traffic index is invalid - index=%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Traffic index is invalid"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-ALLOCFAIL

SEVERITY: Warning

FORMAT: "%s Fail to allocate %s element"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Fail to allocate element"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-INSERTFAIL

SEVERITY: Warning

FORMAT: "%s Fail to insert %s element; index%d"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Fail to insert element"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-NEWBLKALLOCFAIL

SEVERITY: Warning

FORMAT: "%s Fail to allocate new %s block - CONGESTION ON"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Fail to allocate new block - CONGESTION ON"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-5-BUFALLOCFAIL

SEVERITY: Warning

FORMAT: "%s Fail to allocate %s buffer"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Fail to allocate buffer"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-7-NOTENGBUF

SEVERITY: Information

FORMAT: "%s Running out of %s traffic buffers - CONGESTION ON"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Running out of traffic buffers - CONGESTION ON"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

TRAF-7-CONGOFF

SEVERITY: Information

FORMAT: "%s %s CONGESTION OFF"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Turn off congestion"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "unknown"

VCM-5-WARNING

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VCM-7-INFO

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VCM-6-NOTICE

SEVERITY: Notice

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VCM-7-CONN_INSTALLSVC

SEVERITY: Information

FORMAT: "Func %s , Err Cause%s If %lx vpi %d vci %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CM-7-CONN_ALLOCVXL_E

SEVERITY: Information

FORMAT: "Func %s , Err Cause%s If %lx vpi %d vci %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "unknown"

VCM-7-VCM_INSTALL_XCO

SEVERITY: Information

FORMAT: "Func %s API%s, Err Cause%s If %lx vpi %d vci %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VCM-7-VCM_BIG_DELETE_

SEVERITY: Information

FORMAT: "Func %s Cause%s If %lx vpi %d vci %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VCM-7-VCM_RECOMMIT_TI

SEVERITY: Information

FORMAT: "Func %s Cause %s If %lx vpi %d vci %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VCM-7-VCM_FRCE_RESYNC

SEVERITY: Information

FORMAT: "Func %s Cause %s If %lx vpi %d vci %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

VCM-6-NOTICE

SEVERITY: Notice

FORMAT: "%s"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Event explanation comes at later point"

RECOMMENDED ACTION: "Recommended action for this event comes at a later point \n"

REQUIRED INFO: No Required Info

DDTS "unknown"

CSR-7-INFO

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-6-NOTICE

SEVERITY: Notice

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-5-WARNING

SEVERITY: Warning

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-4-ERROR

SEVERITY: Error

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "internal software error"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: "capture log using dsplog -mod CSR"

CSR-7-CONGEST

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-NULL_PTR

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-MALLOC_FAIL

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-TIMEOUT

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-ABORT_FAIL

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-INTF

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-PEP

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-DISK_FAIL

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-START_END

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-BUFFER_UPDT

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CSR-7-REDO_UPDT

SEVERITY: Information

FORMAT: "%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "spvc"

SPVC-4-SWERROR

SEVERITY: Error

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

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "The meaning for variables in the FORMAT string is given below First parameter can be one of following value :

3001 : Connection Management data structure scalling error \

3002 : Error n upping and downing connection \

3003 : Connetion backward bandwidth error \

3004 : Connetion forward bandwidth error \

3005 : NSAP Index error \

3006 : Resync database error \

Second parameter : Logical id of interface \

Third parameter : vpi \

Fourth parameter: vci \

Fifth Parameter : Not used "

RECOMMENDED ACTION: Issue these comamnds on the shell prompt

a) dspver

b) dsplogs

c) dsperrs

d) dsppnports

e) dspcons

f) dspcon

REQUIRED INFO: Collect output of these CLIs

a) dspver b) dsplogs c) dspvers d) dsppnports e) dspcons

f) dspcon for connection in problem

DDTS "axsm-apps/shm"

AXDG-4-ERR

SEVERITY: Error

FORMAT: "AXSM diagnostic error Error 0x%x, %s, %d, 0x%x, 0x%x\n"

FLAG: No Flag

THROTTLING: One Second

EXPLANATION: "Error condition detected. It may cause AXSM diag not to operate properly and require AXSM reset to work properly again. There is a log that asks user to clrdiagerr <slot> to restart online diag. This happens during PXM state change such as switchcc. In this case, there is no need to reset AXSM. Just execute clrdiag as advised. "

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

REQUIRED INFO: "On PXM45

1. dspcds

2. dspcd <slot that experienced the error>

3. dsplog -sl <slot that experienced the error>

4. dsplog -sl <other slot in the pair if redundancy is configured>

5. dsperr for slots specified above.

6. dspdiagcnf

7. dspdiagstatus

8. dspdiagerr online

9. dspdiagerr offline

10. dspdiagstat <slot that experienced the error>

On AXSM

1. dspver

2. dsplns

3. dspports "

AXDG-4-LOGTRC

SEVERITY: Error

FORMAT: "%s error in AXSM diagnostic 0x%x, %s, %d, %d\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Error condition detected. It may cause AXSM diag not to operate properly and require AXSM reset to work properly again. There is a log that asks user to clrdiagerr <slot> to restart online diag. This happens during PXM state change such as switchcc. In this case, there is no need to reset AXSM. Just execute clrdiag as advised. "

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

REQUIRED INFO: "On PXM45

1. dspcds

2. dspcd <slot that experienced the error>

3. dsplog -sl <slot that experienced the error>

4. dsplog -sl <other slot in the pair if redundancy is configured>

5. dsperr for slots specified above.

6. dspdiagcnf

7. dspdiagstatus

8. dspdiagerr online

9. dspdiagerr offline

10. dspdiagstat <slot that experienced the error>

On AXSM

1. dspver

2. dsplns

3. dspports "

AXDG-7-OFFLN

SEVERITY: Information

FORMAT: "%s, %d, %d, %d\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Show offline diagnostic progress"

RECOMMENDED ACTION: "Just information for offline diagnostic progress, no action is required"

REQUIRED INFO: No Required Info

AXDG-7-ONLN_STATUS

SEVERITY: Information

FORMAT: "Online diag status transition detected %s, %s\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Online diag test run success-to-fail or fail-to-success transition is detected. Test run result is integrated (usually takes 5 consecutive test run failures) before online diag failure is reported to PXM. Therefore these events can be logged without PXM declaring AXSM online diag failure, when test run failure is intermittent. Intermittent failure may be caused by temporarily congestion in which case failure should go away after congestion is gone."

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

REQUIRED INFO: "On PXM45

1. dspcds

2. dspcd <slot that experienced the error>

3. dsplog -sl <slot that experienced the error>

4. dspver

5. dspdiagcnf

6. dspdiagerr online

On AXSM

1. dspcd

2. dsdver"

DDTS "boot/shm"

BOOT-5-SERIALHUNGHCR

SEVERITY: Warning

FORMAT: "Serial port is hung (HCR wrong) (hcr=%08lx)."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The serial port is hung (HCR is set wrong), resetting the serial device."

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

BOOT-5-SERIALHUNGREAD

SEVERITY: Warning

FORMAT: "Serial port is hung (read int.) (icr=%08lx)."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The serial port is hung (read interrupt disabled), resetting the serial device."

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

BOOT-5-SERIALHUNGWRITE

SEVERITY: Warning

FORMAT: "Serial port is hung (write int.) (icr=%08lx, count=%d)."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The serial port is hung (write interrupt disabled), resetting the serial device."

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

BOOT-5-ETHERCHIPHUNG

SEVERITY: Warning

FORMAT: "Ethernet chip is hung (%s 0x%x). Restarting chip."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The ethernet chip is hung, resetting the ethernet device."

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

BOOT-2-LANLOSTCARR

SEVERITY: Major Alert

FORMAT: "Ethernet Loss Of Carrier Detected."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The ethernet driver has detected a loss of carrier."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

BOOT-2-LANLOSTCARR_CLR

SEVERITY: Major Alert

FORMAT: "Ethernet Loss Of Carrier Cleared."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The ethernet driver has detected that carrier has returned."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

BOOT-4-HMASTER_NO_HREA

SEVERITY: Error

FORMAT: "BOOT ERR HMASTER is YES, HREADY is NO is detected in %s. FWREADY is not asserted."

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "HMASTER is YES, HREADY is NO. PIO FWREADY bit is not asserted."

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

BOOT-5-UNEXPECTED_INTE

SEVERITY: Warning

FORMAT: "Unexpected Interrupt, vec=%d CauseR=0x%x SR=0x%x ticks=%d"

FLAG: Write to Bram

THROTTLING: No Throttling

EXPLANATION: "These interrupts will only be raised when hardware or device is misconfigured or run into some erroneous conditions. If the same interrupt happens less frequently than the predefined threshold, this message will be logged, otherwise, the board will be reset."

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

BOOT-4-UNEXPECTED_INTE

SEVERITY: Error

FORMAT: "Unexpected interrupt vec=%d CauseR=0x%x SR=0x%x ticks=%d passed threshold=%d in %d ticks"

FLAG: Write to Bram

THROTTLING: No Throttling

EXPLANATION: "These interrupts will only be raised when hardware or device is misconfigured or run into some erroneous conditions. If the same interrupt happens more frequently than the predefined threshold, this message will be logged and the board will be reset."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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: "If the card was reset automatically, core may have been dumped on the hard disk of the Active controller card. If the core was dumped, collect the core. If the card was not reset, call TAC to reset the card in such a way that core would be dumped. Collect the event and error logs.

BOOT-7-BURNBOOT_REQ_DE

SEVERITY: Information

FORMAT: "Burnboot request detected."

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Burnboot signature file was found by backupboot."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

BOOT-4-BURNBOOT_SIGFIL

SEVERITY: Error

FORMAT: "Signature file was found to be present but could not be read. Burnboot aborted.\n"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Signature file for burnboot was found to be present but could not be read. Burnboot aborted."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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: "The burnboot version file was found to be present but could not be read during backupboot."

BOOT-4-BURNBOOT_SIGFIL

SEVERITY: Error

FORMAT: "Signature file content were not in expected format. The file has been renamed to bootver.sav for debugging. Burnboot aborted.\n"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Signature file for burnboot was found to be present but it's contents were not in the expected format. The file is saved as C:/bootver.sav for debugging purposes and card has continued to boot with current boot version. Burnboot aborted."

RECOMMENDED ACTION: Copy the error message exactly as it appears in 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: "After the card boots up, get output of <dsplog -mod SHM_> from the active PXM card. Then ftp to the PXM card in question, and get the file C:/bootver.sav"

BOOT-4-BURNBOOT_SW_ID_

SEVERITY: Error

FORMAT: "Could not extract CTC_SW_ID from the signature file. Burnboot aborted.\n"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Signature file contains the filename to be used for burning boot. Could not extract SW ID from the filename for matching with SW ID in BRAM."

RECOMMENDED ACTION: "Use the old method of boot revision upgrade, i.e., using 'sysFlashBootBurn' in backup boot"

REQUIRED INFO: "The burnboot signature file C:/bootver was read but it's contents could not be parsed well."

BOOT-4-BURNBOOT_VER_IN

SEVERITY: Error

FORMAT: "BRAM flag for burnboot could not be read. Burnboot aborted.\n"

FLAG: Write Bram

THROTTLING: One Tick

EXPLANATION: "Burnboot signature file was found and read, but the corresponding BRAM flag could not be read. Burnboot aborted."

RECOMMENDED ACTION: "Use the old method of boot revision upgrade, i.e., using 'sysFlashBootBurn' in backup boot"

REQUIRED INFO: "On the PXM card in question, go to shellcon and collect output of shell command 'logConsoleShow'"

BOOT-4-BURNBOOT_KEY_IN

SEVERITY: Error

FORMAT: "BRAM key for burnboot could not be read. Burnboot aborted.\n"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Burnboot signature file and the corresponding BRAM flag were read, but the 'key' in BRAM could not be read. Burnboot aborted."

RECOMMENDED ACTION: "Use the old method of boot revision upgrade, i.e., using 'sysFlashBootBurn' in backup boot"

REQUIRED INFO: "On the PXM card, go to shellcon and collect output of shell command 'logConsoleShow'"

BOOT-7-BURNBOOT_SIGFIL

SEVERITY: Information

FORMAT: "Signature file contains version [%d][%d][%d][%d][%d]; Key=[%d].\n"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Displays contents of the burnboot signature file."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: "On the PXM card, go to shellcon and collect output of shell command 'logConsoleShow'"

BOOT-7-BURNBOOT_BRAM_C

SEVERITY: Information

FORMAT: "BRAM contains version [%d][%d][%d][%d][%d]; Key=[%d].\n"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Displays contents of the BRAM flags."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

BOOT-7-BURNBOOT_VERSIO

SEVERITY: Information

FORMAT: "Burnboot Version in BRAM and Sig file were not same. Burnboot aborted.\n"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Burnboot Version in BRAM and Sig file did not match. Burnboot aborted. This would most usually happen if a front card and a back card from different nodes were removed with dangling signature file and BRAM flag for boot upgrade and were put in a new node."

RECOMMENDED ACTION: "Use the old method of boot revision upgrade, i.e., using 'sysFlashBootBurn' in backup boot"

REQUIRED INFO: No Required Info

BOOT-7-BURNBOOT_KEY_MA

SEVERITY: Information

FORMAT: "Burnboot key in BRAM and Sig file were not same. Burnboot aborted.\n"

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Burnboot key in BRAM and Sig file did not match. Burnboot aborted. This would most usually happen if a front card and a back card from different nodes were removed with dangling signature file and BRAM flag for boot upgrade and were put in a new node."

RECOMMENDED ACTION: "Use the old method of boot revision upgrade, i.e., using 'sysFlashBootBurn' in backup boot"

REQUIRED INFO: No Required Info

BOOT-4-BURNBOOT_FAILED

SEVERITY: Error

FORMAT: "Burnboot could not succeed. Aborted. Continuing to boot."

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Burnboot failed because the file was not found or it's checksum/header was not found to be okay."

RECOMMENDED ACTION: "Check for the presence of the file on the card in question, try to ftp it to the card again to make sure it is transferred successfully and retry. If it fails again, use the old method of boot revision upgrade, i.e., using 'sysFlashBootBurn' in backup boot"

REQUIRED INFO: "On the PXM card, go to shellcon and collect output of shell command 'logConsoleShow'"

BOOT-2-BURNBOOT_FAILED

SEVERITY: Major Alert

FORMAT: "Burnboot could not succeed. Aborted. Card is left in removed state for debugging. DO NOT RESET."

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Burnboot was started but during/after writing it, errors were detected and the process aborted midway. Rebooting the card at this point will be fatal and can render the card useless. DO NOT RESET THE CARD. Console port should be attached to the card for debugging."

RECOMMENDED ACTION: "DO NOT RESET THE CARD, it may be rendered useless. Console port should be attached to the card for debugging. Contact TAC for assistance."

REQUIRED INFO: No Required Info

BOOT-7-BURNBOOT_REQ_HA

SEVERITY: Information

FORMAT: "Burnboot request was successfully handled."

FLAG: Write to Bram

THROTTLING: One Tick

EXPLANATION: "Burnboot request was handled well. Cleanup was done and card reset."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

BOOT-4-W_RODATA

SEVERITY: Error

FORMAT: "Write to rodata badAddr=0x%x"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "A task attempted to write into read-only data section. This is often the result of a bug where a task writes to a constant string. It can also happens when writing to a stray pointer. Even though writing to rodata is a bad practise, the operation is allowed (but logged so bug can be fixed). Event is only logged once (further write attempts into rodata are silently allowed). As a result, there can be a memory corruption (most of the time, changing a string is harmless so there might be no consequence)"

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

REQUIRED INFO: "Collect logs (dsplog) around W_RODATA event. Logs should contain a SSI EXCEPTION event corresponding to the read-only data corruption (same bad address in both events). Collect also errors (dsperr), at least error corresponding to SSI exception and containing stack trace."

DDTS "atmsig"

CA-4-CA_IPC_ERROR

SEVERITY: Error

FORMAT: "%s\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Call audit generic IPC 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: "Collect all the logs from dsplog command and outputs of dsppnports, dspconinfo "

CA-4-CA_TIMER_START_

SEVERITY: Error

FORMAT: "%s\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SSI sync timer api returned error."

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

REQUIRED INFO: "Collect all the logs from dsplog command and outputs of dsppnports, dspconinfo"

CA-4-CA_GENERIC_ERRO

SEVERITY: Error

FORMAT: "CA/%s\n"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "call audit task generic 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: "Collect all the logs from dsplog command and outputs of dsppnports, dspconinfo"

CA-6-CA_GENERIC_NOTI

SEVERITY: Notice

FORMAT: "CA/%s\n"

FLAG: No Flag

THROTTLING: No Throttling

EXPLANATION: "Generic notice for call audit task."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

DDTS "alarms"

CAM-5-INVALIDINPUT

SEVERITY: Warning

FORMAT: "One of the inputs to the function %s() was invalid."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for one of the parameters passed in as an argument to the named function was invalid."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAM-5-PARMOUTOFTRANGE

SEVERITY: Warning

FORMAT: "Parm %s is out of range. The range is between %d and %d"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for the named parameter is out of range."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAM-5-PARMINVALID

SEVERITY: Warning

FORMAT: "Parm %s value '0x%x' is invalid to %s."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAM-5-PARMINVLENGTH

SEVERITY: Warning

FORMAT: "Parm %s invalid length of %d to %s. Max=%d Value='%s'"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "API Software Error. The named paramater passed in as an argument to the named function either had a length of zero or exceeded the maximum value specified."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAM-5-FUNCFAIL_STKDUM

SEVERITY: Warning

FORMAT: "%s() SNMP subsystem call to %s() failed. rc=%d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The specified function call failed. It failed with the specified return code. A stack trace was generated."

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

CAM-5-QUEUEFULL

SEVERITY: Warning

FORMAT: "Could not send Alarm Summary %d from slotnum %d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The CAM Client Queue has reached the high water mark"

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "ccma"

DAL-4-DALERR

SEVERITY: Error

FORMAT: "DAL Error %s() line %d %X,%X"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DAL-4-DALERR_STR

SEVERITY: Error

FORMAT: "DAL Error %s() line %d %X,%s"

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: No Explanation

RECOMMENDED ACTION: No Recommended Action

REQUIRED INFO: No Required Info

DDTS "snmp-ma"

CB_S-4-INVALIDINPUT

SEVERITY: Error

FORMAT: "One of the inputs to the function %s() was invalid."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for one of the parameters passed in as an argument to the named function was invalid."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-PARMINVALID

SEVERITY: Error

FORMAT: "Parm %s value '0x%x' is invalid to %s."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-PARMINVLENGTH

SEVERITY: Error

FORMAT: "Parm %s invalid length of %d to %s. Max=%d Value='%s'"

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "API Software Error. The named paramater passed in as an argument to the named function either had a length of zero or exceeded the maximum value specified."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-FUNCFAILSTK

SEVERITY: Error

FORMAT: "%s() SNMP subsystem call to %s() failed. rc=%d."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "The specified function call failed. It failed with the specified return code. A stack trace was generated."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-FUNCFAIL

SEVERITY: Error

FORMAT: "%s() SNMP subsystem call to %s() failed. rc=%d."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The specified function call failed. It failed with the specified return code."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-PARMOUTOFRANGE

SEVERITY: Error

FORMAT: "%s() Parm %s '%d' is out of range %d-%d."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "API Software Error. The parameter value for the named parameter passed in as an argument to the named function is out of the specified range of values."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-MALLOCFAILED

SEVERITY: Error

FORMAT: "%s() Call to ssiMalloc() failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "A call to allocate more memory has 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. memshow"

CB_S-4-OPENTRANSFAIL

SEVERITY: Error

FORMAT: "OpenTransport() failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An attempt to open the IP layer transport failed."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. memshow"

CB_S-4-BINDTRANSFAIL

SEVERITY: Error

FORMAT: "BindTransport() failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An attempt to bind to the IP layer transport failed."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. memshow"

CB_S-4-RCVFRTRNSFAIL

SEVERITY: Error

FORMAT: "ReceiveFromTransport() failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An attempt to receive a message from the IP layer 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. memshow"

CB_S-4-MSGSENDFAIL

SEVERITY: Error

FORMAT: "%s() cntpMsgSend(Queue %s, ptr 0x%x len=%d) failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Attempt to send a control point message 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. memshow"

CB_S-4-MSGRECVFAIL

SEVERITY: Error

FORMAT: "%s() cntpMsgRecv(Queue %s) failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Attempt to receive a control point message buffer 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. memshow"

CB_S-4-BADSRMSLOT

SEVERITY: Error

FORMAT: "%s() Invalid SRM slot %d."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "Invocation of a function using an invalid SRM slot."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-BADCARDTYPE

SEVERITY: Error

FORMAT: "Could not send trap %d from slot %d, sequence num %d."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An attempt to generate a trap resulted in an error. The card type of the originating slot could not be identified."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-INVVARBIND

SEVERITY: Error

FORMAT: "%s() Invalid Varbind type %d."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An invalid varbind was detected during processing."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-SEMCREATEERR

SEVERITY: Error

FORMAT: "%s() cntpSemBCreate() failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Attempt to create the control point semaphore 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. dspsems"

CB_S-4-SEMTAKEERR

SEVERITY: Error

FORMAT: "%s() cntpSemBTake(BasisTrapSem 0x%x) failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Attempt to take the control point semaphore 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. dsptasks

6. dspsems

7. dspsem <semaphore id of BasisTrapSem, 1>"

CB_S-4-SEMGIVEERR

SEVERITY: Error

FORMAT: "%s() cntpSemBGive(BasisTrapSem 0x%x) failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Attempt to give the control point semaphore 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. dsptasks

6. dspsems

7. dspsem <semaphore id of BasisTrapSem, 1>"

CB_S-4-BUFTAKEERR

SEVERITY: Error

FORMAT: "%s() cntpMsgBufTake(dataLn=%d) failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Attempt to take a control point message buffer 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. dsptasks

6. memshow"

CB_S-4-FRMBUFTAKEERR

SEVERITY: Error

FORMAT: "%s() Attempt to get SAR Buffer of len %d failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "Attempt to allocate a SAR Frame buffer 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev

5. dsptasks

6. memshow"

CB_S-7-TOOFEWVARBINDS

SEVERITY: Information

FORMAT: "Trap %d from slot %d has only %d of the mandated Robust Trap varbinds."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An attempted trap generation was disallowed."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

CB_S-7-NOTRAPS

SEVERITY: Information

FORMAT: "%s() Trap dropped because they are disallowed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An attempted trap generation was disallowed."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

CB_S-6-TRAPLOG_WRAP

SEVERITY: Notice

FORMAT: "SNMP Trap log wrapped around."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "The RTM trap log buffer has wrapped around."

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

CB_S-6-RPMPORTCLOSED

SEVERITY: Notice

FORMAT: "Port for RPM slot=%d already closed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An attempt to close an RPM port failed because the port was already closed"

RECOMMENDED ACTION: No action required

REQUIRED INFO: No Required Info

CB_S-4-RPMOPENPORT

SEVERITY: Error

FORMAT: "Opening RPM Port %s for slot=%d failed."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "An attempt to open an RPM port failed."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-OPENPORT

SEVERITY: Error

FORMAT: "%s() Opening Port %s failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "An attempt to open an IPC port failed."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-PROCESSDEQ

SEVERITY: Error

FORMAT: "%s() Call to process_dequeue(0x%x) failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "A call to process_dequeue() 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-CREATEWATCHEDQ

SEVERITY: Error

FORMAT: "%s() Call to create_watched_queue(%s) failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "A call to create_watched_queue() 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-CREATENAMEDPORT

SEVERITY: Error

FORMAT: "%s() Call to ipc_create_named_port(%s) failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "A call to ipc_create_named_port() failed."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-GETPAKMSGFAIL

SEVERITY: Error

FORMAT: "%s() Call to ipc_get_pak_message() failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "A call to ipc_get_pak_message() has 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-IPCSENDMSGFAIL

SEVERITY: Error

FORMAT: "%s() Call to ipc_send_message() failed."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "A call to ipc_send_message() has 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: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-MSG_TOO_SMALL

SEVERITY: Error

FORMAT: "%s() Message of len %d was rejected as too small."

FLAG: Stack Trace

THROTTLING: One Tick

EXPLANATION: "A message of a given length was considered too small."

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

REQUIRED INFO: "On PXM

1. dspcds

2. dsplog

3. dsperr

4. dsprev"

CB_S-4-SOIINITFAIL

SEVERITY: Error

FORMAT: "%s() Could not spawn PXM SOI Task."

FLAG: No Flag

THROTTLING: One Tick

EXPLANATION: "SNMP proxy task SOI spawn 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.