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

DB2S-5-DBSYNC_INVROLE

Table Of Contents

DB2S-5-DBSYNC_INVROLE

DB2S-5-DBSYNC_INVSTATE

DB2S-5-DBSYNC_INVFWDIR

DB2S-5-DBSYNC_INVTX

DB2S-7-DBSYNC_DUPLRESP

DB2S-2-DBSYNC_REPL_FAI

DB2S-4-DBSYNC_EPHNDLR

DB2S-5-DBSYNC_MEM_FAIL

DB2S-5-DBSYNC_TXALLOC

DB2S-5-DBSYNC_IPC_FAIL

DB2S-3-DBSYNC_DOS_FAIL

DB2S-3-DBSYNC_DOS_SZ_E

DB2S-5-DBSYNC_RMT_CPY

DB2S-3-DBSYNC_DOS_RENA

DB2S-5-DBSYNC_DOS_REMO

DB2S-5-DBSYNC_RECVMSG

DB2S-5-DBSYNC_ACTNACK

DB2S-5-DBSYNC_STBNACK

DB2S-5-DBSYNC_INVNACK

DB2S-5-DBSYNC_GEN_FAIL

DB2S-5-DBSYNC_GEN_FAIL

DB2S-5-DBSYNC_GEN_FAIL

DB2S-5-DBSYNC_GEN_FAIL

DB2S-5-DBSYNC_VER_NOTS

DB2S-5-DBSYNC_RETXFAIL

DB2S-7-DBSYNC_BAD_SWID

DB2S-5-UNK_SWID

DB2S-3-DBSYNC_MAX_TRIE

DB2S-5-SYNCFAIL

DB2S-5-SYNCMAXRETRY

DB2S-5-INVREPDIR

DB2S-5-DBSYNC_OS_FAIL

DB2S-5-DBSYNC_INTERNAL

DB2S-5-DBSYNC_INTERNAL

DB2S-5-DBSYNC_WARNING

DB2S-5-DBSYNC_WARNING1

DB2S-4-DBSYNC_BAD_DATA

DB2S-5-DBSYNC_SEM_FAIL

DB2S-7-SLOTABORT

DB2S-7-SYNCBE

DB2S-7-FULLSYNC

DB2S-7-SYNCDONE

DB2S-7-RSTCNFSUC

DB2S-5-RSTCNFFAIL

DB2S-5-UNZIPFAIL

DB2S-7-NODB

DB2S-7-EMPLSLOT

DB2S-5-DBSYNC_UNEXPEVT

DB2S-6-IGNUPDCNT

DB2S-4-UNEXPRESP

DB2S-7-CNFCREATEREQ

DB2S-7-CNFCREATERESP

DB2S-5-CNFZIPFAIL

DB2S-5-REGFORCEFALSE

DB2S-4-REGFORCEDONE

DDTS "diskdb"

DB2V-4-DBVERF_TMRERR

DB2V-5-DBVERF_CTCAPI

DB2V-4-DBVERF_SHMAPI

DB2V-4-DBVERF_DATAXFER

DB2V-5-DBVERF_INVMSGTY

DB2V-5-DBVERF_INVMSGLG

DB2V-5-DBVERF_HDRVAL

DB2V-5-DBVERF_HDRVALMM

DB2V-5-DBVERF_INVRESPI

DB2V-5-DBVERF_LENVAL

DB2V-5-DBVERF_INVVAL

DB2V-5-DBVERF_INVLVAL

DB2V-5-DBVERF_INSUF_BU

DB2V-5-DBVERF_MEM_FAIL

DB2V-5-DBVERF_IPC_FAIL

DB2V-5-DBVERF_RECVMSG

DB2V-5-DBVERF_GEN_FAIL

DB2V-5-DBVERF_GEN_FAIL

DB2V-7-DBVERF_BAD_SWID

DB2V-5-UNK_SWID

DB2V-5-DBVERF_OS_FAIL

DB2V-5-DBVERF_INTERNAL

DB2V-5-DBVERF_INTERNAL

DB2V-5-DBVERF_WARNING

DB2V-5-DBVERF_WARNING1

DB2V-4-DBVERF_BAD_DATA

DB2V-5-DBVERF_SEM_FAIL

DB2V-7-SLOTABORT

DB2V-7-VERFDONE

DB2V-5-DBVERF_UNEXPEVT

DB2V-4-UNEXPRESP

DB2V-4-DBVERF_TASKUNSA

DB2V-3-DBVERF_DOS_FAIL

DDTS "snmp-ma"

SNMP-4-SNMP_ERR

DDTS "axsme-apps"

APS-6-ADD_LN

APS-6-DEL_LN

APS-6-CNF_SFBER

APS-6-CNF_SDBER

APS-6-CNF_WTR

APS-6-CNF_DIR

APS-6-CNF_REV

APS-6-CNF_PROTOCOL

APS-3-SF_DECL

APS-3-SF_DECL_CLEAR

APS-3-SF_BER_DECL

APS-3-SF_BER_DECL_CLE

APS-3-SD

APS-3-SD_CLEAR

APS-2-PSB_FAIL

APS-2-CHAN_MISMATCH

APS-4-PSBF_CLEARED

APS-4-CHAN_MIS_CLEARE

APS-2-FAR_END_FAIL

APS-4-FAR_END_FAIL_CL

APS-2-MODE_MISMATCH

APS-6-MODE_MIS_CLEAR

APS-3-SW_SF

APS-3-SW_SD

APS-3-SW_REV

APS-3-SW_RELEASE

APS-3-SW_LOCK

APS-3-SW_FORCE_WTOP

APS-3-SW_FORCE_PTOW

APS-3-SW_ANNXB_FORCE

APS-3-SW_MAN_WTOP

APS-3-SW_MAN_PTOW

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-4-SW_SF_FAIL

APS-4-SW_SD_FAIL

APS-6-SW_SERVICE

APS-6-PSB_INCONSISTEN

APS-6-PSB_INVALID_DET

APS-3-PRIMARY_SEC_MIS

APS-3-PRIMARY_SEC_SWA

DDTS "drivers"

ATLA-2-AT_INIT_ERROR

ATLA-4-AT_HW_ERROR

ATLA-5-AT_WARNING

DDTS "driver"

DAL-2-DAL_INIT_ERR

DAL-2-DAL_INIT_ERR_ST

DAL-4-DAL_ERR

DAL-4-DAL_ERR_STR

DAL-5-DAL_WARNING

DAL-5-DAL_WARNING_STR

DAL-7-DAL_INFO

DDL-7-DRV_EVENT

DDTS "diag"

DIAG-7-LOG

DIAG-4-ERROR

DDTS "drivers/vsi"

HUMV-2-HV_INIT_ERR

HUMV-2-HV_INIT_ERR_STR

HUMV-4-HV_HW_ERR

HUMV-4-HV_HW_ERR_STR

HUMV-5-HV_WARN

HUMV-5-HV_WARN_STR

HUMV-7-HV_INFO

DDTS "ccma"

OAM-7-LOG

OAM-4-ERROR

DDTS "drivers"

QE-2-QE_INIT_ERR

QE-2-QE_INIT_ERR_STR

QE-4-QE_HW_ERR

QE-4-QE_HW_ERR_STR

QE-5-QE_WARN

QE-5-QE_WARN_STR

QE-7-QE_INFO

DDTS "drivers"

EFE-5-BADFRBNUM

EFE-5-BADPORTNUM

EFE-5-BADCRC

EFE-5-BADHDRSIZE

EFE-5-INITAGAIN

EFE-5-ISRINVOCATION

EFE-5-ISRBEFOREINIT

EFE-5-BADADDRESS

DDTS "diskdb"

ELS-1-FILEOPENFAIL

ELS-3-WRNGEVTLOG

ELS-3-BRAMFAIL

ELS-7-TEST_STACK

DDTS "axsme_apps"

EM-2-PATH_ALARM

EM-3-PATH_ALARM_CLEA

EM-4-EM_ERR_STKTRC

EM-4-EM_ERROR

EM-7-EM_EVENT

EM-2-ONLINE_DIAG_FAI

EM-2-NOVRAM_READ_ERR

EM-2-LINE_HARDWARE_E

EM-2-DAUGHTER_CARD_M

EM-2-PRTSTAT

DDTS "cema"

EM-2-TASKINIT

EM-4-CPICMD

EM-4-DISKERR

EM-4-IPCERR

EM-4-IPCERR_EM_SEND

EM-4-SWERR

EM-4-PHYERR

EM-4-VSIERR

EM-2-DATAERR

EM-6-LOG

EM-4-APSERR

EM-4-GENERR

EM-4-GENERB

EM-2-PHYALM

EM-2-PHYALM_MINOR

EM-2-PHYALM_CLR

EM-2-PRTSTAT

EMRO-2-TASKINIT

EMRO-7-EMINFO

DDTS "axsme_apps"

EM-2-LINE_ALARM

EM-3-REMOTE_LINE_ALA

EM-3-LINE_ALARM_CLEA

DDTS "pnnisys"

SYS-5-QCOUNT

SYS-5-NOTQ

SYS-5-LINKED

SYS-6-TABLEERR

SYS-5-BADLIST

DDTS "ilmi"

ILMI-4-ERROR

ILMI-5-WARNING

DDTS "drivers"

FDM-5-NOFDM

FDM-5-INVALIDPARAM0

FDM-5-NOTFOUND

FDM-5-INITAGAIN

FDM-5-FAILISR

FDM-5-INVALIDPARAM1

FDM-5-INVALIDSTATE0

FDM-5-INVALIDPARAM2

FDM-5-INVALIDSTATE1

FDM-5-INTENFAIL

FDM-5-INVALIDPARAM3

FDM-5-DEACTFAIL

FDM-5-POLLBUSY

FDM-5-LINKINVPARAM

FDM-5-FIFOINVPARAM

FDM-5-FIFOCREATE

FDM-5-ICNFPARAM

FDM-5-ICNFFAIL

FDM-5-ECNFPARAM

FDM-5-ECNFFAIL

FDM-5-IADDPARAM

FDM-5-IADDFAIL

FDM-5-EADDPARAM

FDM-5-EADDFAIL

FDM-5-IDELFAIL

FDM-5-EDELFAIL

FDM-5-ENBDSBPARAM

FDM-5-ENBDSBFAIL

FDM-5-PORTTYPE

FDM-5-RXPROVPARAM

FDM-5-TXPROVPARAM

FDM-5-RXUNPROVPARAM

FDM-5-TAVAIL

FDM-5-TXUNPROVPARAM

FDM-5-IPROVPARAM

FDM-5-IGRPROVGET

FDM-5-EPROVPARAM

FDM-5-EGRPROVGET

DDTS "control-point"

FMGM-7-FM_OPEN_PASSD

FMGM-4-FM_OPEN_FAIL

FMGM-5-FM_INVD_DESC

FMGM-5-FM_INVLD_DESC

FMGM-4-FM_INVLD_SLOT

FMGM-5-FM_MQ_FLSH

FMGM-4-FM_SEM_FAIL

FMGM-5-FM_STAKE_FAIL

FMGM-4-FM_INVD_SLOT

FMGM-4-FM_INVD_FNAME

FMGM-4-FM_INVD_PARAM

FMGM-4-FM_NOT_CBSM

FMGM-4-FM_IPC_ERR

FMGM-4-FM_BUF_ERR

FMGM-4-FM_SCM_FAIL

FMGM-4-FM_MSG_FAIL

FMGM-4-FM_RSP_FAIL

DDTS "control-point/pxm-connmgm"

FILM-7-SM_BOOT_DNLD_PA

FILM-7-SM_FW_DNLD_PASS

FILM-7-PXM_FW_DNLD

FILM-7-PXM_BKUP_DNLD

FILM-7-MSG_SEND_TO_SM

FILM-7-MSG_RCVFROM_SM

FILM-4-BASISTSKSPWNERR

FILM-7-TFTP_NOT_ALLWD

FILM-5-MSGQ_ERR

FILM-5-BUF_ALLOC

FILM-4-PARMINVALID

FILM-5-DISKWRITEFAIL

FILM-5-MSGQFLUSH

FILM-5-MSG2SCMFAIL

FILM-5-RSP_FAIL_RCVD

FILM-5-FAIL_RSP

FILM-4-FW_DNLD_FAILED

FILM-5-FOPEN_FAILED

FILM-7-FOPEN_PASSED

FILM-5-FREAD_FAILED

FILM-5-FWRITE_FAILED

FILM-7-FCLOSE_EVENT

FILM-5-COMPARE_EVT

TFTP-5-SOCKET_ERR

TFTP-4-TASK_SPAWN_ERR

DDTS "frs"

FRS-5-INVALID_INIT_CA

FRS-5-API_CALL_WITHOU

FRS-5-NULL_PTR_ARGS

FRS-5-STATS_ENABLE_UP

FRS-5-RESETDEVICE_INV

FRS-5-INVALID_INTERRU

FRS-6-INTERRUPT_INVOC

FRS-5-INVALID_SELECT_

FRS-5-INVALID_DEVICEN

FRS-5-INVALID_FLAGBIT

FRS-5-INVALID_CONFIGM

FRS-5-INVALID_CHAN_NU

FRS-5-INVALID_PORT_NU

FRS-5-INVALID_CHAN_ST

FRS-5-DMA_ERROR_GET_C

FRS-5-INVALID_PORT_IN

FRS-5-INVALID_PORT_OU

FRS-5-DMA_TIMEOUT

FRS-5-INNER_FUNCTION_

DDTS "ccma"

DAL-4-DALERR

DAL-4-DALERR_STR

DAL-4-DALAVLERR

DAL-7-FPGA

DAL-4-FPGAERR

DDTS "drivers"

FRSM-5-NOS4XD3F

FRSM-5-LDRV_SET_PARAM_

FRSM-5-INVALIDPARAM_LI

FRSM-5-INVALIDPARAM_LI

FRSM-5-INVALIDPARAM_CL

FRSM-5-INVALIDPARAM_CH

FRSM-5-INVALIDPARAM_FE

FRSM-5-INVALIDPARAM_OO

FRSM-5-INITTDMFAIL

FRSM-5-TCC4BADDEVICEID

FRSM-5-TCC4RESETFAIL

FRSM-5-BCC3WRONGREVISI

DDTS "pxm-connmgm"

FTM-7-TASKINIT

FTM-7-MSGPROC

FTM-7-TRAPPROC

DDTS "fw-download"

FTPD-5-FTPD_DIR_FOUND

FTPD-5-FTPD_NON_DIR_FI

FTPD-5-FTPD_OPEN_FAILE

FTPD-4-FTPD_MKDIR_FAIL

FTPD-7-FTPD_VXWORKS_FA

FTPD-7-FTPD_API_ERROR

FTPD-4-FTPD_REPLCTN_FA

FTPD-5-FTPD_REPLCTN_ER

FTPD-5-FTPD_REPLCTN_ER

FTPD-5-FTPD_REP1

FTPD-5-FTPD_REP2

FTPD-4-FTPDLIB1

FTPD-7-FTPDLIB2

FTPD-7-FTPDLIB3

FTPD-7-FTPDLIB4

FTPD-7-FTPDLIB5

FTPD-5-FTPDLIB6

FTPD-7-FTPDLIB7

FTPD-7-FTPDLIB8

FTPD-5-FTPDSIZEMISMATC

FTPD-5-FILELOCKED

FTPD-5-SEMTAKEFAIL

FTPD-5-FTPD_ACCEPT_FAI

FTPD-7-FTPD_CMDSEND_ER

DDTS "hw-poll"

HMM_-2-XBAR_PLANE_RST

HMM_-7-XBAR_DEVPTR_NUL

HMM_-7-DEVPTR_NULL

HMM_-7-INVALID_ERR_SEV

HMM_-7-INVALID_CTC_EVE

HMM_-7-CTC_EVENT_INFO

HMM_-1-IPC_CHAN_FAIL

HMM_-1-CTC_EVT_REG_FAI

HMM_-1-DEVICE_INIT_FAI

HMM_-1-CTC_APP_INIT_FA

HMM_-1-HMM_MALLOC_FAIL

HMM_-7-DEV_EVENT_FAIL

HMM_-7-ERR_STATE_CHANG

HMM_-7-DEV_SEVERITY_RE

HMM_-7-ERR_REPORT_FAIL

HMM_-7-ENDPT_SETUP_FAI

HMM_-7-XBAR_SFRAME_OK

HMM_-2-XBAR_SFRAME_ERR

HMM_-7-HV_SFRAME_OK

HMM_-2-HV_SFRAME_ERR

HMM_-3-SERDES_SYNC_FAI

HMM_-1-XBAR_ALARM_SEND

HMM_-2-BRAM_ENBL_FAIL

DDTS "shm"

HSB-4-FUNCFAILSTK

HSB-4-FUNCFAIL

HSB-4-RAMDBINITFAIL

HSB-4-RAMTBLREGFAIL

HSB-4-RAMSTBYUPDFAIL

HSB-4-DBUPDINVACTION

HSB-4-DBUPDINVELTS

HSB-5-FRMBUFTAKEERR


DB2S-5-DBSYNC_INVROLE

SEVERITY: Warning
FORMAT: "%s Should be called on %s, current role is 0x%x."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The function is expected to be called only on Active card. It is called on the card with specified role."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_INVSTATE

SEVERITY: Warning
FORMAT: "%s Can't be called when Server status is 0x%x."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The function is NOT expected to be called when DB Server is in the given state."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_INVFWDIR

SEVERITY: Warning
FORMAT: "%s Invalid FW Path configured. Expected=%s, configured=%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid path is configured as the first entry in the NON-DB Directory table for FW Path."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_INVTX

SEVERITY: Warning
FORMAT: "%s Invalid Tx Table Index, got %d, should be less than %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync task got a File Replication response with invalid Tx Table index."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-DBSYNC_DUPLRESP

SEVERITY: Information
FORMAT: "%s Duplicate File Replication Response received, Id=%d, Type=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync task received a duplicate response to a file replication request."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-2-DBSYNC_REPL_FAI

SEVERITY: Major Alert
FORMAT: "%s Failed to %s %s to/on the Standby."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The DB Manager Sync module failed to copy/rename/delete given file on the Standby PXM. This could be due to lack of IPC buffers either on Active controller card or Standby controller card. This error could also occur due to failure to access disk either on Standby or on Active controller card. This results in Standby controller card getting out of sync with the Active controller card. Note that this is not considered loss of core redundancy."
RECOMMENDED ACTION: "Don't attempt to switchover untill the importance of the file operation that didn't get replicated is evaluated. Call TAC."
REQUIRED INFO: "Take hot dump on both Active and Standby controller cards. Collect event and error logs."

DB2S-4-DBSYNC_EPHNDLR

SEVERITY: Error
FORMAT: "Error 0x%x in attaching the msg handler to DBSYNC epid 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The DB Manager sync module failed to attach handler function to one of the message queues. This could be due to either bad image or bad hardware. If this error occurs, the card doesn't come up."
RECOMMENDED ACTION: "Try resetting the card one more time. If this error persists, try replacing the card. If this error still persists, call TAC."
REQUIRED INFO: "Save the core. Collect event and error logs."

DB2S-5-DBSYNC_MEM_FAIL

SEVERITY: Warning
FORMAT: "%sError 0x%x on %s 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync encoutered failure when called an SSI MEMORY API function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_TXALLOC

SEVERITY: Warning
FORMAT: "%s Failed to allocate Tx Table Entry"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync encoutered failure when tried to allocate Async Tx Table entry"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_IPC_FAIL

SEVERITY: Warning
FORMAT: "%sError 0x%x %s 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync encountered failure when called an SSI IPC API function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-3-DBSYNC_DOS_FAIL

SEVERITY: Minor Alert
FORMAT: "%sError 0x%x in %s %d, %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The DB Manager Sync module encoutered failure while accessing the hard disk. This could be due to memory corruption or internal error or bad hard disk. If this error occurs while Standby controller card is coming up, it fails to come up. If this error occurs while replicating a file, the file replication operation fails."
RECOMMENDED ACTION: "If this error occured on the Standby controller card while it is coming up, reset the Standby controller card one more time. It the problem still persists and is on the Standby controller card, change the Standby hard disk card. If the problem still persists, call TAC."
REQUIRED INFO: "Save core dump. Collect event and error logs."

DB2S-3-DBSYNC_DOS_SZ_E

SEVERITY: Minor Alert
FORMAT: "%s Actual file size on Active = %d bytes, Copied %d bytes."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The actual number of bytes read from Active controller card doesn't match with the actual size of the file received from Active controller card. This error occurs on the Standby controller card. This could be due to the specified file getting cross linked to another file on the disk. This error could also occur if there is a buffer corruption. This error leads to failure of the file replication operation or disk synchronization while Standby controller is coming up."
RECOMMENDED ACTION: "Remove the file in error on Active controller card and transfer file onto the hard disk. If this error occured while Standby controller card was coming up, reset the Standby controller card. If this error still persists, call TAC."
REQUIRED INFO: "Collect event and error logs."

DB2S-5-DBSYNC_RMT_CPY

SEVERITY: Warning
FORMAT: "%s Copying %s from Active failed. Check the file on ACTIVE."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Remote file copy during File Sync has failed. The actual number of bytes read doesn't match with the actual size of the file received from Active."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-3-DBSYNC_DOS_RENA

SEVERITY: Minor Alert
FORMAT: "%sError 0x%x in %s %s to %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Sync module failed to rename or copy a file. This error could be due to lack of disk space, file system or hard disk failure. This results in failing the file replication operation on the Standby controller card."
RECOMMENDED ACTION: "Change the directory to the path specified in the event and check the available disk space using 'll' command. If it is due to lack of disk space, clean up the disk and reissue the operation that initiated the replication (say, transfering the file to Active controller card or renaming a file in one of the replicated directories etc). If the error is not due to lack of disk space, try changing the Standby controller hard disk."
REQUIRED INFO: "Collect event and error logs."

DB2S-5-DBSYNC_DOS_REMO

SEVERITY: Warning
FORMAT: "%sError 0x%x in %s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Sync module failed to remove a file. This error could be due to file system or hard disk failure. This results in failing the file replication operation on the Standby controller card."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_RECVMSG

SEVERITY: Warning
FORMAT: "Error 0x%x receiving IPC message on DB Sync Port"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync task failed to receive IPC message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_ACTNACK

SEVERITY: Warning
FORMAT: "NACK received from Active Server for %s, reason=0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync task on Standby received a NACK from for the specified request."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_STBNACK

SEVERITY: Warning
FORMAT: "%s NACK received from Standby Server for %d, reason=0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync task or app on Active received a NACK from for the specified request."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_INVNACK

SEVERITY: Warning
FORMAT: "%s Invalid NACK received for %d, reason=0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync task or app received a NACK with invalid request type."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_GEN_FAIL

SEVERITY: Warning
FORMAT: "%s%s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync encountered a general failure while processing the request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_GEN_FAIL

SEVERITY: Warning
FORMAT: "%s. Extra Info- %s<0x%x>"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync detected general failure condition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_GEN_FAIL

SEVERITY: Warning
FORMAT: "%s. Extra Info- %s<0x%x> %s<0x%x>"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync detected general failure condition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_GEN_FAIL

SEVERITY: Warning
FORMAT: "%s. Extra Info- %s<0x%x> %s<0x%x> %s<0x%x>"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync detected general failure condition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_VER_NOTS

SEVERITY: Warning
FORMAT: "Message version %x not supported. Current version is %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync task received an interface message of which the version is incompatible with the version that the DB Server task is running"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_RETXFAIL

SEVERITY: Warning
FORMAT: "%s Error 0x%x on %s epid = %d, &queue = 0x%x, data %s = %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync encoutered failure when called an SSI REXMIT api"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-DBSYNC_BAD_SWID

SEVERITY: Information
FORMAT: "%s SW Id mismatched on slot <%d>, Expected[%d.%d.%d.%d], Received[%d.%d.%d.%d]"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Server detected mismatch on the SW Version received from DB Client's message."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-UNK_SWID

SEVERITY: Warning
FORMAT: "%s Lslot=%d, Prim=%d.%d.%d.%d.%d Sec=%d.%d.%d.%d.%d Given=%d.%d.%d.%d.%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync failed to find the control block for the specified logical slot and given software version as neither the primary or the secondary software version matches with the given software version."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-3-DBSYNC_MAX_TRIE

SEVERITY: Minor Alert
FORMAT: "%s Failed to sync one or more UNSTABLE logical slots"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Sync module has failed to sync the configuration of one or more of the slots. This error occurs when one or more Service Module don't go Active READY, but, are stuck in boot/init state. If a Service Module is stuck in boot/init state, that slot is considered unstable and the Standby controller card skips that slot and continues with the rest while coming up. The Standby controller card attempts to sync a given slot an arbitrary number of times and if the card continues to be unstable, the Standby controller card fails to complete the disk sync. This results in Standby controller card failing to come up."
RECOMMENDED ACTION: "Using the command to display the status of the cards in the node, determine the slots in which the Service Modules are attempting to come up as Active, but are stuck in boot/init state. Remove those cards from the node and reset the Standby controller card."
REQUIRED INFO: "Collect the event and error logs to determine why the Service Module(s) are stuck in boot/init state."

DB2S-5-SYNCFAIL

SEVERITY: Warning
FORMAT: "%s Failed to sync the old version for lslot %d, sync errno 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync failed to sync the old version Db directories for the specified logical slot beacuse of the error specified by the sync errno."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-SYNCMAXRETRY

SEVERITY: Warning
FORMAT: "%s Failed to sync %s version for lslot %d, no tries (%d) > max (%d)"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync failed to sync the old version Db directories for the specified logical slot beacuse the number of attempts exceeded the specified maximum."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-INVREPDIR

SEVERITY: Warning
FORMAT: "Replicated directory %s contains a subdirectory %s. %s is not sync'ed"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync doesn't not sync specified subdirectory in the specified replicated directory."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_OS_FAIL

SEVERITY: Warning
FORMAT: "%sError 0x%x %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync encountered failure when called an SSI-OS function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_INTERNAL

SEVERITY: Warning
FORMAT: "%sInternal failure - %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync detected internal data structure inconsistency"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_INTERNAL

SEVERITY: Warning
FORMAT: "%sInternal failure - Error 0x%x while %s."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync detected internal data structure inconsistency"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_WARNING

SEVERITY: Warning
FORMAT: "%s%s %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync detected a warning condition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_WARNING1

SEVERITY: Warning
FORMAT: "%s%s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Sync detected a warning condition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-4-DBSYNC_BAD_DATA

SEVERITY: Error
FORMAT: "DBSYNC bad data in %s Bad data 0x%x, 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Sync module has detected invalid values in its data structures. This could be due to memory corruption. This results in failing the disk synchronization. As a result, the Standby controller card doesn't come up."
RECOMMENDED ACTION: "Try resetting the card. If the error still persists, try replacing the card."
REQUIRED INFO: "Save core dump. Collect event and error logs."

DB2S-5-DBSYNC_SEM_FAIL

SEVERITY: Warning
FORMAT: "DBSYNC function %s errno = 0x%x while %s 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DbSync failed to create semaphore"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-SLOTABORT

SEVERITY: Information
FORMAT: "DBSYNC Aborted syncing of lslot %d. Reason %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Syncing of the specified slot has been aborted for the specified reason"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-SYNCBE

SEVERITY: Information
FORMAT: "The Standby PXM %s %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Db Sync started/completed (as specified) the specified Sync (DB/Non-DB/Old Version)."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-FULLSYNC

SEVERITY: Information
FORMAT: "The Standby PXM is going to perform a full DB sync for one or more slots"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Db Sync detected that the Standby PXM doesn't have anything for one or more slots and needs to sync everything for those slots from Active PXM."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-SYNCDONE

SEVERITY: Information
FORMAT: "%s%dSending SYNC_DONE Req for Lslot %d Version %d.%d.%d.%d Card State %d Reason%s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Standby DB Sync is sending SYNC_DONE request to Active for the specified logical slot, software version, card state and the reason."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-RSTCNFSUC

SEVERITY: Information
FORMAT: "The configuration successfully restored from %s on STANDBY"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Db Sync successfully restored the configuration from the specified configuration file on the Standby PXM."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-RSTCNFFAIL

SEVERITY: Warning
FORMAT: "Failed to perform restoreallcnf from %s on STANDBY"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Db Sync failed to restore the configuration from the specified configuration file on the Standby PXM. The reason would have been logged prior to this event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-UNZIPFAIL

SEVERITY: Warning
FORMAT: "Failed to unzip %s, errno=0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Db Sync failed to unzip the specified zip file while restoring the configuration on Standby PXM."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-NODB

SEVERITY: Information
FORMAT: "%s No DBs for lslot=%d swId=%d.%d.%d.%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Db Sync on the Active PXM didn't find the DBs for the specified logical slot and swVersion. The DB directory corresponding to this logical slot and the s/w version will be deleted on the Standby."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-EMPLSLOT

SEVERITY: Information
FORMAT: "%s No DB version directories for lslot=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Db Sync on the Standby PXM didn't find any DBs for this logical slot. So, it deletes the directory corresponding to this logical slot."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSYNC_UNEXPEVT

SEVERITY: Warning
FORMAT: "Unexpected %s 0x%x. %s %d, %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Sync task Received CTC events that belongs to other logical slot which the server did not register for."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-6-IGNUPDCNT

SEVERITY: Notice
FORMAT: "Dropped Update Counter (%d) for lslot=%d, swId=%d.%d.%d.%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Db Sync on the Standby PXM dropped the update counters received for specified logical slot and software version because it could not find the slot running that software version."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-4-UNEXPRESP

SEVERITY: Error
FORMAT: "Received unexpected response. Expected type = %d, received type = %d"
FLAG: Write to Bram
THROTTLING: No Throttling
EXPLANATION: "The DB Manager Sync module on Standby contoller card has received a response message for which it is not waiting for from the Active controller card. This could happen when the Active controller card responded to certain requests from Standby controller card after the Standby controller card has timed out waiting for the response and waiting for the response for the next request. This error results in Standby controller card failing to complete the disk synchronization. When this happens, the card gets reset and in most casesit will complete the synchronization in the next attempt."
RECOMMENDED ACTION: "In most cases, it may be intermittent and doesn't persist. But, if it persists, the Standby controller card will be eventually put in FAILED state. If this happens, call TAC."
REQUIRED INFO: "Save the core dump on the Active controller card and Standby controller card. Collect the event and error logs."

DB2S-7-CNFCREATEREQ

SEVERITY: Information
FORMAT: "%s %s 0x%x"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "DbSync's config create request sending /receiving."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-CNFCREATERESP

SEVERITY: Information
FORMAT: "%s %s %s, %d, %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "DbSync's config create response sending/receiving."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-CNFZIPFAIL

SEVERITY: Warning
FORMAT: "Create config zip - %s 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Active Db Sync failed to zip the specified zip file due to incomplete zip, fail zip, fail stat file or fail to response."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-REGFORCEFALSE

SEVERITY: Warning
FORMAT: "Reg in progress forced FALSE. LSlot=%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The Active DB Server forced the registration status for the specified slot to be FALSE so as to allow Standby DB Server sync'ing the specified slot after the Standby DB Server exhausted maximum number of attempts while waiting for the DB registration for the slot to be completed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-4-REGFORCEDONE

SEVERITY: Error
FORMAT: "Reg status forced DONE. LSlot=%d, SwId=%d.%d.%d.%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The Active DB Server forced the registration status for the specified slot/version to be DONE so as to allow Standby DB Server sync'ing the specified slot/version after the Standby DB Server exhausted maximum number of attempts while waiting for the DB registration for the slot/version to be completed. This may result in both Active and Standby DB Server having incomplete DB registration information."
RECOMMENDED ACTION: "Call TAC"
REQUIRED INFO: "Collect event logs and hot-core-dump."

DDTS "diskdb"

DB2V-4-DBVERF_TMRERR

SEVERITY: Error
FORMAT: "%s Error 0x%x creating Sync Timer for File Repl Retx."
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Verify module has failed to create a timer. This could be due to memory shortage or leakage. If this error occurs, the card will not come up."
RECOMMENDED ACTION: "Reset the card one more time and see if it comes up. If the problem persists, try with another controller card."
REQUIRED INFO: "Collect and save the core, event logs and error logs."

DB2V-5-DBVERF_CTCAPI

SEVERITY: Warning
FORMAT: "Error 0x%x on call to %s"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "DB Verify task failed on querying the CTC using the CTC API functions"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-4-DBVERF_SHMAPI

SEVERITY: Error
FORMAT: "Error 0x%x on call to %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Verify module failed to get required information for the Shelf Manager Module. This could be due to lack of IPC buffers or internal error. If this error occurs, regardless of whether it occured on Active controller card or Standby controller card, the Standby controller card doesn't come up."
RECOMMENDED ACTION: "Call TAC"
REQUIRED INFO: "Take hot dump and collect event and error logs."

DB2V-4-DBVERF_DATAXFER

SEVERITY: Error
FORMAT: "%s Error 0x%x on call to %s"
FLAG: Stack Trace|Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Verify module failed while using Data Transfer services. This could be due to internal error. This results in Standby controller card failing to come up."
RECOMMENDED ACTION: "Reset the Standby controller card. If this error still persists, call TAC."
REQUIRED INFO: "Take hot dump of both the Active and Standby controller cards. Collect event and error logs."

DB2V-5-DBVERF_INVMSGTY

SEVERITY: Warning
FORMAT: "%s Message received with Invalid Type = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify task received a message with invalid message type."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_INVMSGLG

SEVERITY: Warning
FORMAT: "%s Invalid Message Length Lg in Hdr %d should be <= %d+%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify task received a message with invalid message Length. The length in header should be less than or equal to the Msg Len given by the IPC + message header size."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_HDRVAL

SEVERITY: Warning
FORMAT: "Header Validation Invalid %s-expected 0x%x LSlot 0x%x MsgType 0x%x MsgLen 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify task received a message with invalid header contents."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_HDRVALMM

SEVERITY: Warning
FORMAT: "Header Validation Invalid %s-expected [0x%x-0x%x] LSlot 0x%x MsgType 0x%x MsgLen 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify task received a message with invalid header contents."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_INVRESPI

SEVERITY: Warning
FORMAT: "%s Invalid File Response, expected = 0x%x or 0x%x, received 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Application/DB Verify task received an invalid response to File Replication request."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_LENVAL

SEVERITY: Warning
FORMAT: "%s Invalid message length, expected >= %d, received %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify task received a message with invalid message length."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_INVVAL

SEVERITY: Warning
FORMAT: "%s Invalid %s, expected >= %d, received %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verf task received a message with invalid value for the specified field."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_INVLVAL

SEVERITY: Warning
FORMAT: "%s Invalid %s, expected <= %d, received %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Verify task received an invalid value for the specified field."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_INSUF_BU

SEVERITY: Warning
FORMAT: "%s Insufficient buffer SendLen=%d, Need %d more, Total Avail=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verf task preparing a response message and the buffer that has been allocated is insufficient."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_MEM_FAIL

SEVERITY: Warning
FORMAT: "%sError 0x%x on %s 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify encoutered failure when called an SSI MEMORY API function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_IPC_FAIL

SEVERITY: Warning
FORMAT: "%sError 0x%x %s 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify encountered failure when called an SSI IPC API function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_RECVMSG

SEVERITY: Warning
FORMAT: "Error 0x%x receiving IPC message on DB Verf Port"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify task failed to receive IPC message"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_GEN_FAIL

SEVERITY: Warning
FORMAT: "%s%s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Verify encountered a general failure while processing the request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_GEN_FAIL

SEVERITY: Warning
FORMAT: "%s. Extra Info- %s<0x%x>"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Verify detected general failure condition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-7-DBVERF_BAD_SWID

SEVERITY: Information
FORMAT: "%s SW Id mismatched on slot <%d>, Expected[%d.%d.%d.%d], Received[%d.%d.%d.%d]"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Server detected mismatch on the SW Version received from DB Client's message."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-UNK_SWID

SEVERITY: Warning
FORMAT: "%s Lslot=%d, Prim=%d.%d.%d.%d.%d Sec=%d.%d.%d.%d.%d Given=%d.%d.%d.%d.%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Verify failed to find the control block for the specified logical slot and given software version as neither the primary or the secondary software version matches with the given software version."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_OS_FAIL

SEVERITY: Warning
FORMAT: "%sError 0x%x %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verify encountered failure when called an SSI-OS function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_INTERNAL

SEVERITY: Warning
FORMAT: "%sInternal failure - %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verf detected internal data structure inconsistency"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_INTERNAL

SEVERITY: Warning
FORMAT: "%sInternal failure - Error 0x%x while %s."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Verf detected internal data structure inconsistency"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_WARNING

SEVERITY: Warning
FORMAT: "%s%s %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Verify detected a warning condition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_WARNING1

SEVERITY: Warning
FORMAT: "%s%s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Verify detected a warning condition"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-4-DBVERF_BAD_DATA

SEVERITY: Error
FORMAT: "DBVERF bad data in %s Bad data 0x%x, 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Verify module has detected invalid values in its data structures. This could be due to memory corruption."
RECOMMENDED ACTION: "Try resetting the card. If the error still persists, try replacing the card."
REQUIRED INFO: "Save core dump. Collect event and error logs."

DB2V-5-DBVERF_SEM_FAIL

SEVERITY: Warning
FORMAT: "DBVERF function %s errno = 0x%x while %s 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DbVerf failed to create semaphore"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-7-SLOTABORT

SEVERITY: Information
FORMAT: "DBVERF Aborted DiskVerf of lslot %d. Reason %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Verifying of the specified slot has been aborted for the specified reason"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-7-VERFDONE

SEVERITY: Information
FORMAT: "%s%dSending SYNC_DONE Req for Lslot %d Version %d.%d.%d.%d Card State %d Reason%s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Standby DB Verify is sending VERF_DONE request to Active for the specified logical slot, software version, card state and the reason."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-5-DBVERF_UNEXPEVT

SEVERITY: Warning
FORMAT: "Unexpected %s 0x%x. %s %d, %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Verf task Received CTC events that belongs to other logical slot which the server did not register for."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2V-4-UNEXPRESP

SEVERITY: Error
FORMAT: "Received unexpected response. Expected type = %d, received type = %d"
FLAG: Write to Bram
THROTTLING: No Throttling
EXPLANATION: "The DB Manager Verify module on Standby contoller card has received a response message for which it is not waiting for from the Active controller card. This could happen when the Active controller card responded to certain requests from Standby controller card after the Standby controller card has timed out waiting for the response and waiting for the response for the next request. This error results in Standby controller card failing to complete the disk verification."
RECOMMENDED ACTION: "In most cases, it may be intermittent and doesn't persist. If it persists, call TAC."
REQUIRED INFO: "Save the core dump on the Active controller card and Standby controller card. Collect the event and error logs."

DB2V-4-DBVERF_TASKUNSA

SEVERITY: Error
FORMAT: "A call to ssiTaskUnsafe for Task 0x%x failed."
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "A call to ssiTaskUnsafe failed while attempting to unlock a resource. This task cannot currently be deleted."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

DB2V-3-DBVERF_DOS_FAIL

SEVERITY: Minor Alert
FORMAT: "%sError 0x%x in %s %d, %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The DB Manager Verf module encoutered failure while accessing the hard disk. This could be due to memory corruption or internal error or bad hard disk."
RECOMMENDED ACTION: "Reset the Standby controller card. It the problem still persists and is on the Standby controller card, change the Standby hard disk card. If the problem still persists, call TAC."
REQUIRED INFO: "Save core dump. Collect event and error logs."

DDTS "snmp-ma"

SNMP-4-SNMP_ERR

SEVERITY: Error
FORMAT: "SNMP Agent Error %s at line %d in file %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error is logged as a result of errors in SNMP master-agent"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

DDTS "axsme-apps"

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: One Tick
EXPLANATION: "Aps Line Added.The event log would show the working and protection line indices. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

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: One Tick
EXPLANATION: "Aps Line Pair deleted"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-CNF_SFBER

SEVERITY: Notice
FORMAT: "Aps Line Reconfigured. SF BER changed %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "SF Ber changed by user"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-CNF_SDBER

SEVERITY: Notice
FORMAT: "Aps Line Reconfigured. SD BER changed %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "SD Ber changed by user."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-CNF_WTR

SEVERITY: Notice
FORMAT: "Aps Line Reconfigured. WTR changed %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Wait To Restore time limit changed by user This indicates the time the selector will continue to select traffic from the protection line even after the fault condition in the working line is repaired/removed before switching back to the working line"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-CNF_DIR

SEVERITY: Notice
FORMAT: "Aps Line Reconfigured. Direction changed %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Directionality (Uni/Bi) is changed by user. The event is logged only when there is a change in the direction."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-CNF_REV

SEVERITY: Notice
FORMAT: "Aps Line Reconfigured. Revertive changed %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Revertive mode changed by user The event is logged only when there is change in the mode."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-CNF_PROTOCOL

SEVERITY: Notice
FORMAT: "Aps Line Reconfigured. APS Protocol(Bellcore/ITU) changed %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "APS Protocol(Bellcore/ITU) changed by user. If ITU Protocol is configured then directionality info (UNI/BI) in K2 byte will not be indicated"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SF_DECL

SEVERITY: Minor Alert
FORMAT: "APS Signal Fail Error (LOS/LOF/AIS-L) on %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "APS Signal Fail condition detected due to LOS/LOF/AIS-L on the line."
RECOMMENDED ACTION: "Check the line cable on local end and remote end. Check the backcard status on local end and remote end."
REQUIRED INFO: No action required. Operational event log only.

APS-3-SF_DECL_CLEAR

SEVERITY: Minor Alert
FORMAT: "APS Signal Fail Error (LOS/LOF/AIS-L) Cleared on %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Aps Signal Fail alarm condition cleared. Logging the event for informational purpose."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SF_BER_DECL

SEVERITY: Minor Alert
FORMAT: "APS Signal Fail Due to Excessive Bit Errors on %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Aps SF due to excessive BIP errors. It happens when the bit error rate exceeds the SF threshold on a line."
RECOMMENDED ACTION: "Check the line cable on local end and remote end. Check the backcard status on local end and remote end."
REQUIRED INFO: No action required. Operational event log only.

APS-3-SF_BER_DECL_CLE

SEVERITY: Minor Alert
FORMAT: "APS Signal Fail Due to Excessive Bit Errors Cleared on %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Aps SF due to excessive BIP errors cleared.It happens when the bit error rate falls below the SF threshold on a line.Logging the event for informational purpose."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SD

SEVERITY: Minor Alert
FORMAT: "APS Signal Degrade Error on %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Aps Line Signal Degrade alarm detected.It happens when the bit error rate exceeds the SD threshold on a line."
RECOMMENDED ACTION: "Check the line cable on local end and remote end. Check the backcard status on local end and remote end."
REQUIRED INFO: No action required. Operational event log only.

APS-3-SD_CLEAR

SEVERITY: Minor Alert
FORMAT: "APS Signal Degrade Error Cleared on %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Aps Line SD cleared.It happens when the bit error rate falls below the SD threshold on a line. Logging the event for informational purpose."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-2-PSB_FAIL

SEVERITY: Major Alert
FORMAT: "APS Protection Switch Byte Failure on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps PSBF Failure occurs if the APS receives an invalid or an inconsistent K1 byte from remote end. A Protection Switching Byte Defect is detected upon receipt of invalid/inconsistent K1 byte. If the defect persists for 2.5s then a Protection Switching Byte Failure is declared"
RECOMMENDED ACTION: "Please check the APS configuration on the remote end. Check if the backcards are connected properly.
If redundancy is configured then check if the aps mini backplane
is correctly engaged and the backcards are inserted properly with
correct alignment on the aps backplane. Also verify that the lines
are properly terminated and the contact is good. For further information.
please refer to the Bellcore GR-253-CORE document."
REQUIRED INFO: No action required. Operational event log only.

APS-2-CHAN_MISMATCH

SEVERITY: Major Alert
FORMAT: "APS Channel Mismatch on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Chan Mismatch Failure occurs when the channel number indicated by both ends are different."
RECOMMENDED ACTION: "Please check if the APS is configured correctly and the APS on the far end is functioning properly.For further information please refer to the Bellcore GR-253-CORE document"
REQUIRED INFO: No action required. Operational event log only.

APS-4-PSBF_CLEARED

SEVERITY: Error
FORMAT: "APS Protection Switch Byte Failure Cleared on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "PSBF has been Cleared"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-4-CHAN_MIS_CLEARE

SEVERITY: Error
FORMAT: "APS Channel Mismatch Failure Cleared on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "APS Channel mismatch Failure Cleared."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-2-FAR_END_FAIL

SEVERITY: Major Alert
FORMAT: "APS Far End Protection Line Failure on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Far End Protection Line Failure occurs when the near end receives a signal fail code for the protection line. This indicates that the far end is no longer receiving the near end's request or considers the near end's request to be invalid. For further information please refer to the Bellcore GR-253-CORE document"
RECOMMENDED ACTION: "Please check if the cables at the far end are connected properly."
REQUIRED INFO: No action required. Operational event log only.

APS-4-FAR_END_FAIL_CL

SEVERITY: Error
FORMAT: "APS Far End Protection Line Failure Cleared on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Far End Protection Line Failure Cleared"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-2-MODE_MISMATCH

SEVERITY: Major Alert
FORMAT: "APS Mode Mismatch on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps mode mismatch detected.This happens when one end is configured in Unidirectional and the other end is in Bidirectional Mode. It can also happen if one end is added in 1+1 architecture and the other end is in 11.This could cause a change in the operating mode.For further information please refer to the Bellcore GR-253-CORE document"
RECOMMENDED ACTION: "Check if the mode or the architecture should be same. If they are supposed to be different then this condition will occur."
REQUIRED INFO: No action required. Operational event log only.

APS-6-MODE_MIS_CLEAR

SEVERITY: Notice
FORMAT: "APS Mode Mismatch Cleared on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps mode mismatch cleared. RxK2 byte mode is same as the Provisioned mode. This could cause a change in the APS operating mode."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_SF

SEVERITY: Minor Alert
FORMAT: "APS Internal Switch due to Aps Signal Fail %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Switch due to SF. Traffic may have been affected. It indicates a switch away from the affected line. Logging for informational purposes only."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_SD

SEVERITY: Minor Alert
FORMAT: "APS Internal Switch due to Aps Signal Degrade %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Switch due to SD. This command occurs when there's a signal degrade on the line. It indicates a switch away from the affected line. Logging for informational purposes only."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_REV

SEVERITY: Minor Alert
FORMAT: "APS Reverse Request Switch %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Reverse Request Switch is generated in response to a remote request like WTR, Forced switch or SF/SD. This causes a switch away from the affected line. This is generated only for APS configured in bidirectional mode Logging for informational purposes only."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_RELEASE

SEVERITY: Minor Alert
FORMAT: "APS Switch Cleared. No Pending Request for %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Selector is released. No pending request present Logging for informational purposes only."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_LOCK

SEVERITY: Minor Alert
FORMAT: "User Requested APS Lockout successful %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Lockout happened due to User Request. Traffic may have been disturbed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_FORCE_WTOP

SEVERITY: Minor Alert
FORMAT: "User Requested APS Forced Work->Prot successful %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Forced W->P Switch happened due to User Request. Traffic may have been disturbed. This will make the APS select from the protection line."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_FORCE_PTOW

SEVERITY: Minor Alert
FORMAT: "User Requested APS Forced Prot->Work successful %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Forced P->W Switch happened due to User Request Traffic may have been disturbed. This will make the APS select from the working line."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_ANNXB_FORCE

SEVERITY: Minor Alert
FORMAT: "User Requested APS Forced Switch successful %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Forced Switch (Annex-B protocol) happened due to User Request. Traffic may have been disturbed. This will make the APS select from the other Working Section."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_MAN_WTOP

SEVERITY: Minor Alert
FORMAT: "User Requested APS Manual Work->Prot successful %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Manual W->P Switch happened due to User Initiated Request. Logging the event for informational purpose."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-SW_MAN_PTOW

SEVERITY: Minor Alert
FORMAT: "User Requested APS Manual Prot->Work successful %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Manual P->W Switch happened due to User Initiated Request. Logging the event for informational purpose."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-4-SW_CLEAR_FAIL

SEVERITY: Error
FORMAT: "Cannot do APS Switch Clear %s workLN = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Clear Fail. Check the reason displayed in the eventlog."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-4-SW_LOCK_FAIL

SEVERITY: Error
FORMAT: "Cannot do APS Switch Lockout %s workLN = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "APS Line Lockout command failed. Check the reason displayed in the eventlog."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-4-SW_FORCE_WTOP_F

SEVERITY: Error
FORMAT: "Cannot do APS Switch Forced Work->Prot %s workLN = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Forced W->P Switch fail"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-4-SW_FORCE_PTOW_F

SEVERITY: Error
FORMAT: "Cannot do APS Switch Forced Prot->Work %s workLN = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Forced P->W Switch fail"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-4-SW_MAN_WTOP_FAI

SEVERITY: Error
FORMAT: "Cannot do APS Manual Switch Work->Prot %s workLN = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Manual W->P Switch fail"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-4-SW_MAN_PTOW_FAI

SEVERITY: Error
FORMAT: "Cannot do APS Manual Switch Prot->Work %s workLN = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Manual P->W Switch fail"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

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: One Tick
EXPLANATION: "Aps Switch due to SF fail.In normal operation, such an error should never get reported. This may result in traffic loss."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-4-SW_SD_FAIL

SEVERITY: Error
FORMAT: "APS Internal Switch due to Aps Signal Degrade FAILED %s workLN = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Switch due to SD fail.In normal operation, such an error should never get reported. This may result in traffic loss."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-SW_SERVICE

SEVERITY: Notice
FORMAT: "User Requested APS Service Switch workLN = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Aps Line Service Switch requested by user is successful. Traffic may have been disturbed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-PSB_INCONSISTEN

SEVERITY: Notice
FORMAT: "APS Inconsistent K1 Detected on %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Inconsistent K1 byte Detection"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-6-PSB_INVALID_DET

SEVERITY: Notice
FORMAT: "APS Invalid K1 req 0x%x and chan 0x%x detected on %s"
FLAG: No Flag
THROTTLING: Hundred Milliseconds
EXPLANATION: "Invalid K1 byte Detection"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-PRIMARY_SEC_MIS

SEVERITY: Minor Alert
FORMAT: "APS Primary Section Mismatch detected on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Primary Section Mismatch Detected. This happens when APS at one end has a different Primary Section than the other end."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

APS-3-PRIMARY_SEC_SWA

SEVERITY: Minor Alert
FORMAT: "APS Primary Section Swap on %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Primary Section Swap Occured. This happens when the working sections are swapped and the primary section indicates the other working section."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No action required. Operational event log only.

DDTS "drivers"

ATLA-2-AT_INIT_ERROR

SEVERITY: Major Alert
FORMAT: "ATLAS Init Error Atlas No %d, line %d, errno %d, info %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: " A hardware error is detected by the ATLAS driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. do core dump"

ATLA-4-AT_HW_ERROR

SEVERITY: Error
FORMAT: "ATLAS HW Error Atlas No %d, line %d, errno %d, info %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: " A hardware error has been detected by ATLAS drive during runtime In normal operation, this kind of error should never happen. This error needs to be analyzed by TAC and possibly by the development team."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. do core dump or register dump
3. dspchancnt on affected connections"

ATLA-5-AT_WARNING

SEVERITY: Warning
FORMAT: "ATLAS Warning Atlas No %d, line %d, errno %d, info %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "A warning condition has been detected by ATLAS driver."
RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection
6. do core dump or register dump"
ATLA-7-AT_INFO
SEVERITY: Information
FORMAT: "ATLAS Info Atlas No %d, line %d, errno %d, info %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "ATLAS Driver Informational Log"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "driver"

DAL-2-DAL_INIT_ERR

SEVERITY: Major Alert
FORMAT: "DAL Init Err line %d errno=0x%X,0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the DAL module during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-2-DAL_INIT_ERR_ST

SEVERITY: Major Alert
FORMAT: "DAL Init Err line %d errno=0x%X,0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the DAL module driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-4-DAL_ERR

SEVERITY: Error
FORMAT: "DAL Err line %d errno=0x%X,0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-4-DAL_ERR_STR

SEVERITY: Error
FORMAT: "DAL Err line %d errno=0x%X,0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-5-DAL_WARNING

SEVERITY: Warning
FORMAT: "DAL Warning line %d errno=0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an warning detected by the DAL module."
RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection"

DAL-5-DAL_WARNING_STR

SEVERITY: Warning
FORMAT: "DAL Warning line %d errno=0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an warning detected by the DAL module."
RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection"

DAL-7-DAL_INFO

SEVERITY: Information
FORMAT: "DAL Info line %d errno=0x%X,0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DAL Informational Event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDL-7-DRV_EVENT

SEVERITY: Information
FORMAT: "DDL_EVENT: %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Device Driver Layer Event - more info can be obtained from the error string printed out - applications calling the drivers would log appropriate errors - this is to get detailed info on the specific error experienced by the driver"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "diag"

DIAG-7-LOG

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

DIAG-4-ERROR

SEVERITY: Error
FORMAT: " OfflnDiag error %s %s\n"
FLAG: Stack Trace
THROTTLING: No Throttling
EXPLANATION: "Indicates an internal software error has been detected by OfflnDiag"
RECOMMENDED ACTION: "Call your Cisco technical support representative and pass the captured info to the representative."
REQUIRED INFO: "Capture the following info from the switch On pxm45 1>dspcd 2>dspver 3>dspcds 4>dsppnports 5>dsplog -sl <slot number of Service Module> 6>dsperr -sl <slot number of Service Module> On the Service Module(SM) 1>dspcd 2>dspver 3>dsplns 4>dspports 5>dspparts 6>dspapslns (for SONET cards)"

DDTS "drivers/vsi"

HUMV-2-HV_INIT_ERR

SEVERITY: Major Alert
FORMAT: "HUMVEE Init Err line %d, errno=0x%X 0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the HUMVEE driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

HUMV-2-HV_INIT_ERR_STR

SEVERITY: Major Alert
FORMAT: "HUMVEE Init Err line %d, errno=0x%X 0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the HUMVEE driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

HUMV-4-HV_HW_ERR

SEVERITY: Error
FORMAT: "HUMVEE Err line %d, errno=0x%X 0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates a hardware error detected by the HUMVEE driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. do core dump or register dump
3. dspchancnt on affected connection "

HUMV-4-HV_HW_ERR_STR

SEVERITY: Error
FORMAT: "HUMVEE Err line %d, errno=0x%X 0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates a hardware error detected by the HUMVEE driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. do core dump or register dump
3. dspchancnt on affected connection "

HUMV-5-HV_WARN

SEVERITY: Warning
FORMAT: "HUMVEE Warning line %d, errno=0x%X 0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an warning detected by the HUMVEE driver."
RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection
6. do core dump or register dump "

HUMV-5-HV_WARN_STR

SEVERITY: Warning
FORMAT: "HUMVEE Warning line %d, errno=0x%X 0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an warning detected by the HUMVEE driver."
RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection
6. do core dump or register dump "

HUMV-7-HV_INFO

SEVERITY: Information
FORMAT: "HUMVEE Info line %d, errno=0x%X 0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "HUMVEE Informational Event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "ccma"

OAM-7-LOG

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

OAM-4-ERROR

SEVERITY: Error
FORMAT: "OAM error %s %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates a software error detected by the oam task. Need to contact TAC for the problem."
RECOMMENDED ACTION: "Call your Cisco technical support representative and pass the captured info to the representative."
REQUIRED INFO: "Capture the following info from the switch On pxm45 1>dspcd 2>dspver 3>dspcds 4>dsppnports 5>dsplog -sl <slot number of Service Module> 6>dsperr -sl <slot number of Service Module> On the Service Module(SM) 1>dspcd 2>dspver 3>dsplns 4>dspports 5>dspparts 6>dspapslns (for SONET cards)"

DDTS "drivers"

QE-2-QE_INIT_ERR

SEVERITY: Major Alert
FORMAT: "QE Init Err: line %d, errno=0x%X : 0x%X,0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the QE1210 driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives:"
REQUIRED INFO: " On PXM45:
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module:
1. dspcd "

QE-2-QE_INIT_ERR_STR

SEVERITY: Major Alert
FORMAT: "QE Init Err line %d, errno=0x%X 0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the QE1210 driver during initialization. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

QE-4-QE_HW_ERR

SEVERITY: Error
FORMAT: "QE Err line %d, errno=0x%X 0x%X,0x%X"
FLAG: Stack Trace|Write to Bram
THROTTLING: No Throttling
EXPLANATION: "Indicates a hardware error detected by the QE1210 driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. do core dump or register dump
3. dspchancnt on affected connection "

QE-4-QE_HW_ERR_STR

SEVERITY: Error
FORMAT: "QE Err line %d, errno=0x%X 0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates a hardware error detected by the QE1210 driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. do core dump or register dump
3. dspchancnt on affected connection"

QE-5-QE_WARN

SEVERITY: Warning
FORMAT: "QE Warning line %d, errno=0x%X 0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an warning detected by the QE1210 driver."
RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection
6. do core dump or register dump "

QE-5-QE_WARN_STR

SEVERITY: Warning
FORMAT: "QE Warning line %d, errno=0x%X 0x%X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates an warning detected by the QE1210 driver."
RECOMMENDED ACTION: "Sometime the warnings are expected. If there is some traffic loss, please capture the following information and contact your Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspchancnt on the problem connection
6. do core dump or register dump "

QE-7-QE_INFO

SEVERITY: Information
FORMAT: "QE Info line %d, errno=0x%X 0x%X,0x%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "QE1210 Informational Event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "drivers"

EFE-5-BADFRBNUM

SEVERITY: Warning
FORMAT: "FRB number %d is unacceptable."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

EFE-5-BADPORTNUM

SEVERITY: Warning
FORMAT: "Port number %d is unacceptable."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

EFE-5-BADCRC

SEVERITY: Warning
FORMAT: "CRC size %d is unacceptable."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

EFE-5-BADHDRSIZE

SEVERITY: Warning
FORMAT: "Header size %d is unacceptable."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

EFE-5-INITAGAIN

SEVERITY: Warning
FORMAT: "%s() Driver already initialized."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "IFE driver getting initialized more than once."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

EFE-5-ISRINVOCATION

SEVERITY: Warning
FORMAT: "EFE error Error Reg=(0x%08x)"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "EFE Error Occured."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

EFE-5-ISRBEFOREINIT

SEVERITY: Warning
FORMAT: "%s() ISR called before Init."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "EFE ISR is called before efeInit."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

EFE-5-BADADDRESS

SEVERITY: Warning
FORMAT: "Bad pointer %p"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "diskdb"

ELS-1-FILEOPENFAIL

SEVERITY: Fatal
FORMAT: "failed to open event log file"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "failed to open event log file"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

ELS-3-WRNGEVTLOG

SEVERITY: Minor Alert
FORMAT: "EventLog Server receives a message other than ERR_LOG_MSG"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "EventLog Server Task receives a message other than the message type of ERR_LOG_MSG"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

ELS-3-BRAMFAIL

SEVERITY: Minor Alert
FORMAT: "BRAM checksum failed %ud, %u d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "BRAM checksum failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

ELS-7-TEST_STACK

SEVERITY: Information
FORMAT: "%s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Test for Stack Trace"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "axsme_apps"

EM-2-PATH_ALARM

SEVERITY: Major Alert
FORMAT: "%s Failure on %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Specified failure has been detected on the path. A failure is declared after persistency check on a defect. A failure typically indicates data loss at local or remote end. Path failures are generaly a result of transport failure, external to the switch."
RECOMMENDED ACTION: "Check the external transport equipment and the far end equipment to identify the root cause."
REQUIRED INFO: "dsppathalm will identify the failure(s) for the specified path."

EM-3-PATH_ALARM_CLEA

SEVERITY: Minor Alert
FORMAT: "%s Failure Cleared on %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Specified failure on the path is now cleared. Failures are cleared after persistency check on clearing of associated defect."
RECOMMENDED ACTION: "No action is required. The event is logged to inform the network operator that a previous local/remote failure is now cleared."
REQUIRED INFO: No Required Info

EM-4-EM_ERR_STKTRC

SEVERITY: Error
FORMAT: "EM ERROR: %s\n"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Indicates an internal error detected by the EM application. It needs to be analyzed by TAC and possibly by the development team. In normal operation, such an error should never get reported."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco technical support representative: "
REQUIRED INFO: " On PXM45:
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
On Service Module:
1. dspcd
2. dsplns
3. dspports
4. dspparts
5. dspapslns (for SONET cards) "

EM-4-EM_ERROR

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

EM-7-EM_EVENT

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

EM-2-ONLINE_DIAG_FAI

SEVERITY: Major Alert
FORMAT: "ONLINE DIAG ERROR %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicate failure in cell path test. If this happens on an active card with redundancy ready, it will cause a card switch over. Software will not take any action if this happens on an active card without redundancy or on a standby card. When this happens on an active card, the card will experience traffic loss and its likely to see some other errors"
RECOMMENDED ACTION: "First please collect the following info. If this happens on an active card without redundancy or on a standby card, manually reset the card. If reset fails, need to replace the front card.
Then call your Cisco technical support representative for the problem."
REQUIRED INFO: "Capture the following info On Pxm45 1> dspcd 2> dspcds 3> dsplog -sl <slot number of service module> 4> dsperr -sl <slot number of service module> On Service Module(SM) 1> dspcd 2> dspver 3> dspports"

EM-2-NOVRAM_READ_ERR

SEVERITY: Major Alert
FORMAT: "NOVRAM Read Error %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error indicates a failure reading the NOVRAM. This failure can be for one of the following NOVRAMs
1. Front Card NOVRAM
2. Daughter Card NOVRAM
3. Back Card NOVRAM"
RECOMMENDED ACTION: "If the error is indicated for Front Card or Daughter Card NOVRAM, please replace the Front Card. Replace the Back Card if error is indicated for Back Card NOVRAM. In most cases, NOVRAM read failures are a direct result of a hardware failure. However, if you suspect that the error was caused due a certain operator action or a system event, please capture the following information and contact your Cisco support representative "
REQUIRED INFO: "Please capture following information on PXM45
1. dspcds
2. dspcd <slot>
3. dsplog
On Service Module, please capture the following information
1. dspcd
2. dsplns "

EM-2-LINE_HARDWARE_E

SEVERITY: Major Alert
FORMAT: "Line Hardware Error on line %d.%d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error indicates a hardware failure for the specified line. The failure is typicaly due to a front-card hardware problem."
RECOMMENDED ACTION: "Please replace the Front Card if the problem persists across reboots. Note that if this error is detected on a standby card, it will automaticaly reboot. If the error is detected on an active card, the card will continue to function. However, the dspcds command on PXM45 will show that the card state is Active-F. Contact your Cisco support representative if you suspect that a certain operator action or a system event caused this error."
REQUIRED INFO: "Please capture the information with following commands on the active service module
1. dspcd
2. dsplns
3. dspalms
Please capture the system log with dsplog <slot> command on PXM45."

EM-2-DAUGHTER_CARD_M

SEVERITY: Major Alert
FORMAT: "Unknown/Missing Daughter Card on bay %d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This error indicates a failure in recognizing the Daughter Card in the specified bay. This can happen due to one of the followng reasons
1. Daughter Card NOVRAM is not readable
2. Daughter Card Type specified by NOVRAM is not supported
3. A Daughter Card is not installed.
This error is detecting during the booting phase. "
RECOMMENDED ACTION: "Please replace the Front Card as it is not usable. Note that this error will take the card in Active-F state. If the error is detected on a standby card, it will cause the card to reset. Please capture following information and contact your Cisco support representative if you suspect that a certain operator action or a system event caused this error "
REQUIRED INFO: "Please capture following information on PXM45
1. dspcds
2. dspcd <slot>
3. dsplog
On Service Module, please capture the following information
1. dspcd
2. dsplns "

EM-2-PRTSTAT

SEVERITY: Major Alert
FORMAT: "Port State Port%d Oper State%s \n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Change in port operation state. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_ERROR to make it more visible for customer."
RECOMMENDED ACTION: "Port operation state changes according to line state. Check line for alarms and take appropriate corrective actions on physical line."
REQUIRED INFO: No Required Info

DDTS "cema"

EM-2-TASKINIT

SEVERITY: Major Alert
FORMAT: "ERROR 0x%x CEMA application initialization failure"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Error occurred during CEMA application initialization. The error is fatal if it prevents the AXSM from going to the card ready state. When this happens, AXSM gets 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: "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. dspver
If AXSM does eventually come up, on AXSM
1. dspcd
2. dsdver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only)
7. dspilmis
8. dsplmis
Note whether event is logged during to card reset or switchover."

EM-4-CPICMD

SEVERITY: Error
FORMAT: "ERROR 0x%x General CPI command failure"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error occurred while processing CPI command"
RECOMMENDED ACTION: "Retry CLI commands. Failure can sometimes be temporarily. If error persists, copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information."
REQUIRED INFO: "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. dspver
On AXSM
1. dspcd
2. dspver "

EM-4-DISKERR

SEVERITY: Error
FORMAT: "Disk failure Error 0x%x, %s, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error is detected while accessing disk from AXSM. The detail error type is the Error field in the event log. If this happens as a result of CLI, it simply means that disk update for this CLI fails and the CLI is rejected. If this happens during card initialization, some configuration prior to card reset may be lost and service can probably be impacted. This event log is usually accompanied by a corresponding SSI disk event log which contains more error details."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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. dspver
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only)
7. dspilmis
8. dsplmis
Note whether event is logged during card reset or switchover. If card is reset, note if it is a consequence of setrev/loadrev/runrev. "

EM-4-IPCERR

SEVERITY: Error
FORMAT: "IPC failure Error 0x%x, %s, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error occurred while making IPC function call. This event log is usually accompanied by a corresponding IPC event log."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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. dspver
On AXSM
1. dspcd
2. dspver "

EM-4-IPCERR_EM_SEND

SEVERITY: Error
FORMAT: "IPC failure Error 0x%x, %s, 0x%x, 0x%x\n"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Error occurred while making IPC function call. This event log is usually accompanied by a corresponding IPC event log. This is called when Error in sendEmReq."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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. dspver
On AXSM
1. dspcd
2. dspver "

EM-4-SWERR

SEVERITY: Error
FORMAT: "SW error Error 0x%x, %s, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Miscellaneous software error occurred."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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. dspver
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only) "

EM-4-PHYERR

SEVERITY: Error
FORMAT: "PHY error Error 0x%x in function %s, line %d.%d\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error occurred while making PHY module function call. It can be service impacting if error results in line not being configured properly. "
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "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. dspver
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspapslns (SONET card only) "

EM-4-VSIERR

SEVERITY: Error
FORMAT: "VSI error Error 0x%x, %s, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error occurred while making VSI module function call. It can be service impacting if error results in port and partitions not being configured properly. "
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "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. dspver
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts "

EM-2-DATAERR

SEVERITY: Major Alert
FORMAT: "EM database consistency error 0x%x, %s, %d, %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Database inconsistency has been detected. For example, a port exists on a line that has not been upped. In this case, the port is deleted as a corrective action to restore database consistency. Database consistency is only checked during card reset of switchover. The resulting change can cause system to work differently than before inconsistency is detected."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "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.
7. cd DDB2
8. change to disk DB directory for primary slot. For example, slot 11
disk DB is in directory LS11.
9. dir
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only)
Note whether event is logged during card reset or switchover. If card is reset, note if it is a consequence of setrev/loadrev/runrev. "

EM-6-LOG

SEVERITY: Notice
FORMAT: "EM LOG %s, %d, %ld, %ld\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Miscellaneous software error occurred."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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.
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only) "

EM-4-APSERR

SEVERITY: Error
FORMAT: "APS error Error 0x%x, %s, %d, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error occurred while making APS module function call."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "On 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.
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspapslns (SONET cards only) "

EM-4-GENERR

SEVERITY: Error
FORMAT: "%s error Error 0x%x, %s, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error as depicted in event log occurred."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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.
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only) "

EM-4-GENERB

SEVERITY: Error
FORMAT: "%s error Error 0x%x, %s, 0x%x, 0x%x, 0x%x\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error as depicted in event log occurred."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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.
On AXSM
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only) "

EM-2-PHYALM

SEVERITY: Major Alert
FORMAT: "PHY line alarm Line %d.%d %s\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Red line alarm has been detected. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_MAJOR_ALERT at the request by customer to make it more visible."
RECOMMENDED ACTION: "Line alarms are part of normal operation. Use dspalm, dspln and dspatmcnf type commands to find out alarms and line configuration. Check physical line cables to see that they are properly installed. Check that the line configurations are correct since alarms can sometimes be due to incompatible line type. Follow normal network procedure to isolate line fault in network."
REQUIRED INFO: "Issue dspver on AXSM to get AXSM SW version and date image was built."

EM-2-PHYALM_MINOR

SEVERITY: Major Alert
FORMAT: "PHY line alarm minor Line %d.%d %s\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Minor line alarm has been detected. It can be remote alarm or minor APS-relalted alarm. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_MAJOR_ALERT at the request by customer to make it more visible."
RECOMMENDED ACTION: "Line alarms are part of normal operation. Use dspalm, dspln and dspatmcnf type commands to find out alarms and line configuration. Check physical line cables to see that they are properly installed. Check that the line configurations are correct since alarms can sometimes be due to incompatible line type. Follow normal network procedure to isolate line fault in network."
REQUIRED INFO: "Issue dspver on AXSM to get AXSM SW version and date image was built."

EM-2-PHYALM_CLR

SEVERITY: Major Alert
FORMAT: "PHY line alarm cleared Line %d.%d %s\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Line alarm as mentioned in event is cleared. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_MAJOR_ALERT at the request by customer to make it more visible."
RECOMMENDED ACTION: "No action is required. The event is logged to inform the network operator that a previous local/remote failure is now cleared."
REQUIRED INFO: No Required Info

EM-2-PRTSTAT

SEVERITY: Major Alert
FORMAT: "Port State Port%d Oper State%s \n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Change in port operation state. Note that this event is informational only and not a software operation error. The severity is elevated to EVENT_MAJOR_ALERT to make it more visible for customer."
RECOMMENDED ACTION: "Port operation state changes according to line state. Check line for alarms and take appropriate correction actions on physical line."
REQUIRED INFO: No Required Info

EMRO-2-TASKINIT

SEVERITY: Major Alert
FORMAT: "EM Root failure 0x%x, %s, %d, %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Error occurred during CEMA application initialization. The error is fatal if it prevents the AXSM from going to the card ready state. When this happens, AXSM gets 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: "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. dspver
If AXSM does eventually come up, on AXSM
1. dspcd
2. dsdpver
3. dsplns
Note whether event is logged during to card reset or switchover."

EMRO-7-EMINFO

SEVERITY: Information
FORMAT: "%s\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "This event is for developer information purpose."
RECOMMENDED ACTION: "No Action is required since it is only informational and not service impacting."
REQUIRED INFO: "None Required"

DDTS "axsme_apps"

EM-2-LINE_ALARM

SEVERITY: Major Alert
FORMAT: "Local Failure on%sLine %d.%d, Cause %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Specified line has a local failure. A failure is declared after persistency check on the defect. It indicates that the switch is unable to receive user data from the specified line. The log also identifies the cause for the failure. Failures can be declared due to removal of back card,cable disconnection or any physical disconnection with the remote equipment."
RECOMMENDED ACTION: "Check if the back card and cable are installed. Check the status of remote equipment. This log typicaly indicates an external problem."
REQUIRED INFO: "dspalm will identify the failure(s) for the specified line."

EM-3-REMOTE_LINE_ALA

SEVERITY: Minor Alert
FORMAT: "Remote Failure on%sLine %d.%d, Cause %s\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Specified line has a remote-end failure. A failure is declared after persistency check on the defect. It indicates that the data transmited on the specified line is not reaching the other end. As a result the remote end is reporting a defect."
RECOMMENDED ACTION: "Check if the back card and cable are installed. This log typicaly indicates an external problem."
REQUIRED INFO: "dspalm will identify the failure(s) for the specified line."

EM-3-LINE_ALARM_CLEA

SEVERITY: Minor Alert
FORMAT: "All Failures Cleared on%sLine %d.%d.\n"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "All failures (local and remote) on the line are cleared"
RECOMMENDED ACTION: "No action is required. The event is logged to inform the network operator that a previous local/remote failure is now cleared."
REQUIRED INFO: No Required Info

DDTS "pnnisys"

SYS-5-QCOUNT

SEVERITY: Warning
FORMAT: "Bad %s %x count %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An internal software error occurred."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."

SYS-5-NOTQ

SEVERITY: Warning
FORMAT: "%s didn't find %x in queue %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An internal software error occurred."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."

SYS-5-LINKED

SEVERITY: Warning
FORMAT: "Bad %s of %x in queue %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An internal software error occurred."
RECOMMENDED ACTION: "If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."

SYS-6-TABLEERR

SEVERITY: Notice
FORMAT: "%s table %s damaged %s."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "An internal table entry became corrupt."
RECOMMENDED ACTION: "Copy the message exactly as it appears, and report it your technical support representative."
REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."

SYS-5-BADLIST

SEVERITY: Warning
FORMAT: "Regular expression access check with bad list %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "A software error occurred."
RECOMMENDED ACTION: "Copy the error message exactly as it appears, and report it to your technical support representative."
REQUIRED INFO: "Capture all the log when problem happened by CLI command (dsplog,dspver,dsperrs) on controller."

DDTS "ilmi"

ILMI-4-ERROR

SEVERITY: Error
FORMAT: "ILMI Internal Err%s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "It describes internal errors(ILMI protocol related) for ILMI module on PNNI controller"
RECOMMENDED ACTION: "Check the ILMI status on each interface and figure out which interface has ILMI status changed or error.Record the abnormal behavior and gather all the ILMI and interface related information, and then contact your TAC representative."
REQUIRED INFO: "Collect node info on PNNI controller using dspver,dspcds,dsppnports; collect ILMI log using (dsplog -mod ILMI);if specific port is known,collect ILMI info on this port using (dsppnilmi portId).It is also helpful to gather IFM log using (dsplog -mod IFM)"

ILMI-5-WARNING

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

DDTS "drivers"

FDM-5-NOFDM

SEVERITY: Warning
FORMAT: "%s() FREEDM device not exist."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Unable to detect FREEDM device."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-INVALIDPARAM0

SEVERITY: Warning
FORMAT: "%s() Invalid parameters pFdmDev = 0x%x bDoReset = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-NOTFOUND

SEVERITY: Warning
FORMAT: "%s() FREEDM# %d Incorrect device ID = 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Unrecognized FREEDM device ID."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-INITAGAIN

SEVERITY: Warning
FORMAT: "%s() Driver already initialized."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "FREEDM driver got initialize more than once."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-FAILISR

SEVERITY: Warning
FORMAT: "%s() Fail to install ISR."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed to install ISR."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-INVALIDPARAM1

SEVERITY: Warning
FORMAT: "%s() Invalid parameter pFdmDev = 0x%x pParam = 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-INVALIDSTATE0

SEVERITY: Warning
FORMAT: "%s() not in eFDM_RESET state - state = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Must be in eFDM_RESET state to do initialization."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-INVALIDPARAM2

SEVERITY: Warning
FORMAT: "%s() Invalid parameter pFdmDev = 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid FREEDM device descriptor pointer."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-INVALIDSTATE1

SEVERITY: Warning
FORMAT: "%s() Not in eFDM_INIT state - state = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Must be in eFDM_INIT to do activation."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-INTENFAIL

SEVERITY: Warning
FORMAT: "%s() Failed to enable interrupt."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Cannot enable interrupt."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-INVALIDPARAM3

SEVERITY: Warning
FORMAT: "%s() Invalid parameter pFdmDev = 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid FREEDM device descriptor pointer."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-DEACTFAIL

SEVERITY: Warning
FORMAT: "%s() Deactivation failed."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed to deactivate the FREEDM device."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-POLLBUSY

SEVERITY: Warning
FORMAT: "%s() FREEDM# = %d Offset = 0x%x Bit mask = 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "FREEDM device busy."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-LINKINVPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameter(s) pFdmDev = %x portType = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-FIFOINVPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid param pFdmDev=%x u16BlockStart=%d u16BlockEnd=%d txRx=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameters."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-FIFOCREATE

SEVERITY: Warning
FORMAT: "%s() Unable to create channel FIFO %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed FIFO create."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-ICNFPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameter pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-ICNFFAIL

SEVERITY: Warning
FORMAT: "%s() Ingress port configuration failed."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Port configuration failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-ECNFPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameter pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-ECNFFAIL

SEVERITY: Warning
FORMAT: "%s() Egress port configuration failed."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Port configuratiuon failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-IADDPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameter pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-IADDFAIL

SEVERITY: Warning
FORMAT: "%s() Ingress port add failed."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Port add failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-EADDPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameter pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-EADDFAIL

SEVERITY: Warning
FORMAT: "%s() Egress port add failed."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Port add failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-IDELFAIL

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

FDM-5-EDELFAIL

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

FDM-5-ENBDSBPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameter action = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-ENBDSBFAIL

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

FDM-5-PORTTYPE

SEVERITY: Warning
FORMAT: "%s() Non-supported port type %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Port type not supported."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-RXPROVPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameters pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-TXPROVPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameters pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-RXUNPROVPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameters pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-TAVAIL

SEVERITY: Warning
FORMAT: "%s() Timeout waiting for TAVAIL"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Transaction still pending."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-TXUNPROVPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameters pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-IPROVPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameters pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-IGRPROVGET

SEVERITY: Warning
FORMAT: "%s() Ingress channel is not provisioned"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Channel not provisioned."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-EPROVPARAM

SEVERITY: Warning
FORMAT: "%s() Invalid parameters pParam = %x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid parameter."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FDM-5-EGRPROVGET

SEVERITY: Warning
FORMAT: "%s() Egress channel is not provisioned."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Channel not provisioned."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "control-point"

FMGM-7-FM_OPEN_PASSD

SEVERITY: Information
FORMAT: "%s slotNum %d, reqType %d, Msg %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Open API of the specified file passed."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FMGM-4-FM_OPEN_FAIL

SEVERITY: Error
FORMAT: "%s slotNum %d, reqType %d, Msg %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Open API of the specified file failed."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-5-FM_INVD_DESC

SEVERITY: Warning
FORMAT: "%s status %d, routine %p, Msg %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid request descriptor."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-5-FM_INVLD_DESC

SEVERITY: Warning
FORMAT: "%s Msg %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid request descriptor."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_INVLD_SLOT

SEVERITY: Error
FORMAT: "%s slot number is %d, Msg is %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid slot number."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-5-FM_MQ_FLSH

SEVERITY: Warning
FORMAT: "%s %s Message queue id is %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error trying to flush message queue"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_SEM_FAIL

SEVERITY: Error
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Semaphore creation 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: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-5-FM_STAKE_FAIL

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Semaphore take 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: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_INVD_SLOT

SEVERITY: Error
FORMAT: "%s slot number is %d, card state is %d, card type is %d, Msg is %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid slot number."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_INVD_FNAME

SEVERITY: Error
FORMAT: "%s Msg is %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid File Name."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_INVD_PARAM

SEVERITY: Error
FORMAT: "%s parameter is %d, Msg is %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid input parameter."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_NOT_CBSM

SEVERITY: Error
FORMAT: "%s slot number is %d, card type is %d, Msg is %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Card Type not supported."
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_IPC_ERR

SEVERITY: Error
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Obtained ERROR from an IPC message."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_BUF_ERR

SEVERITY: Error
FORMAT: "%s %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Unable to allocate frame buffer."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_SCM_FAIL

SEVERITY: Error
FORMAT: "%s slotNum is %d, operation is %d, request is %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Unable to do intercard communication thru SCM."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_MSG_FAIL

SEVERITY: Error
FORMAT: "%s %s Original message sent slotNum is %d, operation is %d, request is %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Bad response from SM"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

FMGM-4-FM_RSP_FAIL

SEVERITY: Error
FORMAT: "%s %s opType received is %d,status received is %d, blockNum received is %d,offSet received is %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failure response received from SM"
RECOMMENDED ACTION: This error inidicates the cause of rejecting requests for any file upload/download from narrow band service modules. Each error contains a error message. 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 for further analysis.
REQUIRED INFO: Please collect the output of CLIs dspver, dspcds, dsplog

DDTS "control-point/pxm-connmgm"

FILM-7-SM_BOOT_DNLD_PA

SEVERITY: Information
FORMAT: "%s Backup Boot Download passed for Slot %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Backup Boot was downloaded to the Service Module successfully."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FILM-7-SM_FW_DNLD_PASS

SEVERITY: Information
FORMAT: "%s Firmware Download passed for Slot %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Firmware was downloaded to the Service Module successfully."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FILM-7-PXM_FW_DNLD

SEVERITY: Information
FORMAT: "Downloaded PXM Revision %s "
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "This information event indicates that PXM Firmware has been downloaded."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FILM-7-PXM_BKUP_DNLD

SEVERITY: Information
FORMAT: "Downloaded PXM Backup Boot, Revision %s "
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "PXM Backup BootCode has been downloaded."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FILM-7-MSG_SEND_TO_SM

SEVERITY: Information
FORMAT: "%s %s slotNum is %d, opType is %d, fileType is %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Message send to SM."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FILM-7-MSG_RCVFROM_SM

SEVERITY: Information
FORMAT: "%s %s optype is %d, status is %d, blockNum is %d, offSet is %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Message received from SM."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FILM-4-BASISTSKSPWNERR

SEVERITY: Error
FORMAT: "%s Spawn Task Failed , TaskName %s, Slot No %d, File Type %d"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Unable to create a new task."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

FILM-7-TFTP_NOT_ALLWD

SEVERITY: Information
FORMAT: "%s slotNum %d, fileType %d, card type %d, Msg %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Specified command not allowed for this Card type"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FILM-5-MSGQ_ERR

SEVERITY: Warning
FORMAT: "QName %s, SlotNo %d, FileType %d, Msg %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Unable to create a message queue."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

FILM-5-BUF_ALLOC

SEVERITY: Warning
FORMAT: "%s %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Unable to allocate frame buffer."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

FILM-4-PARMINVALID

SEVERITY: Error
FORMAT: "Parm %s value '0x%x' is invalid to %s."
FLAG: Stack Trace
THROTTLING: One Second
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: No Required Info

FILM-5-DISKWRITEFAIL

SEVERITY: Warning
FORMAT: "%s Write to disk failed, fileType is %d"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Unable to write file to disk."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

FILM-5-MSGQFLUSH

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

FILM-5-MSG2SCMFAIL

SEVERITY: Warning
FORMAT: "%s slotNum is %d, opType is %d, fileType is %d"
FLAG: Stack Trace | Dump Trace
THROTTLING: One Second
EXPLANATION: "Unable to do intercard communication thru SCM."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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

FILM-5-RSP_FAIL_RCVD

SEVERITY: Warning
FORMAT: "%s %s opType received is %d, status received is %d, blockNum received is %d, offSet received is %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Failure response received from SM"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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

FILM-5-FAIL_RSP

SEVERITY: Warning
FORMAT: "%s %s Original message sent slotNum is %d, opType is %d, fileType is %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Bad response from SM"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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

FILM-4-FW_DNLD_FAILED

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

FILM-5-FOPEN_FAILED

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

FILM-7-FOPEN_PASSED

SEVERITY: Information
FORMAT: "%s slotNum %d, fileType %d, Msg %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Open API of the specified file passed."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FILM-5-FREAD_FAILED

SEVERITY: Warning
FORMAT: "%s fD %d, slotNo %d, fileType %d, Msg %s"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "File read failed."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

FILM-5-FWRITE_FAILED

SEVERITY: Warning
FORMAT: "%s fD %d, slotNo %d, fileType %d, Msg %s"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "File write failed."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

FILM-7-FCLOSE_EVENT

SEVERITY: Information
FORMAT: "%s slotNum %d, fileType %d, Msg %s"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Closing the specified file."
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

FILM-5-COMPARE_EVT

SEVERITY: Warning
FORMAT: "%s Param1 %d, Param2 %d, slotNo %d, fileType %d, Msg %s"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Card Type doesn't match the image header."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the 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

TFTP-5-SOCKET_ERR

SEVERITY: Warning
FORMAT: "%s Failed to Receive on Socket %d"
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: "Received Error while trying to read data from tftp socket."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

TFTP-4-TASK_SPAWN_ERR

SEVERITY: Error
FORMAT: "%s Spawn Task Failed , TaskName %s, TaskPriority %d, TaskStackSize %d"
FLAG: Stack Trace
THROTTLING: One Second
EXPLANATION: "Spawning of a task failed."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

DDTS "frs"

FRS-5-INVALID_INIT_CA

SEVERITY: Warning
FORMAT: "FRS INVALID_INIT_CALL Code=(%u) #InitCalls=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-API_CALL_WITHOU

SEVERITY: Warning
FORMAT: "FRS API_CALL_WITHOUT_INIT Code=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-NULL_PTR_ARGS

SEVERITY: Warning
FORMAT: "FRS NULL_PTR_ARGS Code=(%u) Ptr=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-STATS_ENABLE_UP

SEVERITY: Warning
FORMAT: "FRS STATS_ENABLE_UPDATE_ERROR Code=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-RESETDEVICE_INV

SEVERITY: Warning
FORMAT: "FRS RESETDEVICE_INVALID_DEV_BITMAP Code=(%u) BitMap=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_INTERRU

SEVERITY: Warning
FORMAT: "FRS INVALID_INTERRUPT_TYPE Code=(%u) INVALID_INTERRUPT_TYPE=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-6-INTERRUPT_INVOC

SEVERITY: Notice
FORMAT: "FRS INTERRUPT_INVOCATION Reg=(0x%08x)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_SELECT_

SEVERITY: Warning
FORMAT: "FRS INVALID_SELECT_DECODE Code=(%u) selectDecode=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_DEVICEN

SEVERITY: Warning
FORMAT: "FRS INVALID_DEVICENUM Code=(%u) DeviceNum=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_FLAGBIT

SEVERITY: Warning
FORMAT: "FRS INVALID_FLAGBITPOS Code=(%u) flagBitPos=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_CONFIGM

SEVERITY: Warning
FORMAT: "FRS CONFIGMAP Code=(%u) configMap=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_CHAN_NU

SEVERITY: Warning
FORMAT: "FRS INVALID_CHAN_NUM_ARG Code=(%u) Chan=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_PORT_NU

SEVERITY: Warning
FORMAT: "FRS INVALID_PORT_NUM_ARG Code=(%u) Port=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_CHAN_ST

SEVERITY: Warning
FORMAT: "FRS INVALID_CHAN_STATS_RANGE Code=(%u) ChanBeg=(%u) nChans=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-DMA_ERROR_GET_C

SEVERITY: Warning
FORMAT: "FRS DMA_ERROR_GET_CHAN_STATS Code=(%u) ChanBeg=(%u) nChans=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_PORT_IN

SEVERITY: Warning
FORMAT: "FRS INVALID_PORT_IN_LMI_ALM_CALL Code=(%u) Port=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INVALID_PORT_OU

SEVERITY: Warning
FORMAT: "FRS INVALID_PORT_OUT_OF_LMI_ALM_CALL Code=(%u) Port=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-DMA_TIMEOUT

SEVERITY: Warning
FORMAT: "FRS DMA_TIMEOUT Code=(%u) srcPtr=(%u) destPtr=(%u) nBytes=(%u) TickCount=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRS-5-INNER_FUNCTION_

SEVERITY: Warning
FORMAT: "FRS INNER_FUNCTION_FAILED Code=(%u)\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "ccma"

DAL-4-DALERR

SEVERITY: Error
FORMAT: "DAL Error %s() line %d %X,%X"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-4-DALERR_STR

SEVERITY: Error
FORMAT: "DAL Error %s() line %d %X,%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates a hardware error detected by the DAL module driver. It needs to be analyzed by TAC and possibly by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd "

DAL-4-DALAVLERR

SEVERITY: Error
FORMAT: "DAL Internal Error line %d %s,%u,%u,%u"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates error in DAL AVL tree. It needs to be analyzed by the development team. In normal operation, this error should never occur."
RECOMMENDED ACTION: "Please capture the following information and call your Cisco Technical Support Representatives"
REQUIRED INFO: " On PXM45
1. dspcd <slot that experienced the error>
2. dspred
3. dsplog -sl <slot the experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above
On Service Module
1. dspcd
2. dspcons -filt 8"

DAL-7-FPGA

SEVERITY: Information
FORMAT: "FPGA upload/dnload %s, %s, 0x%x, 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates FPGA upload/dnload progress"
RECOMMENDED ACTION: "No action is required. Event is logged to show FPGA upload/dnload progress"
REQUIRED INFO: No Required Info

DAL-4-FPGAERR

SEVERITY: Error
FORMAT: "FPGA upload/dnload error %s, %s, 0x%x, 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Indicates error is encountered during FPGA upload/dnload progress"
RECOMMENDED ACTION: "No action is required. Event is logged to show FPGA upload/dnload progress"
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. dspver
On FRSM12
1. dspcd
2. dsdpver
3. If shell command access is available, excecute dspFpgaRevs shell command "

DDTS "drivers"

FRSM-5-NOS4XD3F

SEVERITY: Warning
FORMAT: "%s() FRMR device not exist."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Unable to detect SUNI4XD3F device."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-LDRV_SET_PARAM_

SEVERITY: Warning
FORMAT: "%s() DRV_set param fails line#%d, data %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "LDRV_set param fails."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-INVALIDPARAM_LI

SEVERITY: Warning
FORMAT: "%s() Invalid parameter line#%d, lineType %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-INVALIDPARAM_LI

SEVERITY: Warning
FORMAT: "%s() Invalid parameter line#%d, lineLength %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-INVALIDPARAM_CL

SEVERITY: Warning
FORMAT: "%s() Invalid parameter line#%d, txClkSrc %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-INVALIDPARAM_CH

SEVERITY: Warning
FORMAT: "%s() Invalid parameter line#%d, checkAIS %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-INVALIDPARAM_FE

SEVERITY: Warning
FORMAT: "%s() Invalid parameter line#%d, FEAC criteria %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-INVALIDPARAM_OO

SEVERITY: Warning
FORMAT: "%s() Invalid parameter line#%d, OOF criteria %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed parameter check."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-INITTDMFAIL

SEVERITY: Warning
FORMAT: "%s() Init TDM fails."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed TDM initialization."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-TCC4BADDEVICEID

SEVERITY: Warning
FORMAT: "%s() TCC4 has wrong device ID."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Wrong TCC4 device ID."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-TCC4RESETFAIL

SEVERITY: Warning
FORMAT: "%s() TCC4 reset fails."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "TCC4 fails during reset."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FRSM-5-BCC3WRONGREVISI

SEVERITY: Warning
FORMAT: "%s() Backcard BCC3 has wrong revision."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Wrong backcard BCC3 revision."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "pxm-connmgm"

FTM-7-TASKINIT

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

FTM-7-MSGPROC

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

FTM-7-TRAPPROC

SEVERITY: Information
FORMAT: "Trap Proc Error %s %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Trap Processing Errors"
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

DDTS "fw-download"

FTPD-5-FTPD_DIR_FOUND

SEVERITY: Warning
FORMAT: "EVNT Directory %s found, No need to create"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: " found directory"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-5-FTPD_NON_DIR_FI

SEVERITY: Warning
FORMAT: "ERRfound a non directory entry of name %s found."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: " found a non directory entry of name FTPD"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-5-FTPD_OPEN_FAILE

SEVERITY: Warning
FORMAT: "ERR unable to open dir/file %s "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: " unable to call open for FTPD"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-4-FTPD_MKDIR_FAIL

SEVERITY: Error
FORMAT: "ERR unable to do create directory %s "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: " unable to create dir for FTPD"
RECOMMENDED ACTION: "Make sure C\TMP exists. If not, create one and re-ftp the file. If the problem persist, please contact TAC"
REQUIRED INFO: "Capture the output of 'dir C'"

FTPD-7-FTPD_VXWORKS_FA

SEVERITY: Information
FORMAT: "EVNT%s %s "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: " unable to call vxworks call"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-7-FTPD_API_ERROR

SEVERITY: Information
FORMAT: "EVNTApi returns error, api=%s, errno 0x%x "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: " API returns error. Need to look at errno"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-4-FTPD_REPLCTN_FA

SEVERITY: Error
FORMAT: "ERR Replication request FAILED for %s, errno=0x%x"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Replication request failed"
RECOMMENDED ACTION: "File replication to standby PXM failed. Contact TAC to manually copy the file over."
REQUIRED INFO: "Capture the following commands
1) dsplog -mod FTPD
2) dsplog -mod SSI
3) dsplog "

FTPD-5-FTPD_REPLCTN_ER

SEVERITY: Warning
FORMAT: "ERR %s NOT REPLICATED ON STBY "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Replication request failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-5-FTPD_REPLCTN_ER

SEVERITY: Warning
FORMAT: "ERR %s not copied.Exists as %s "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Replication request failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-5-FTPD_REP1

SEVERITY: Warning
FORMAT: "EVNTFTP Replicate usr file %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "log event to note replication request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-5-FTPD_REP2

SEVERITY: Warning
FORMAT: "EVNTFTP from file %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "log event to note replication request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

FTPD-4-FTPDLIB1

SEVERITY: Error
FORMAT: "ERR - %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "error spawning ftp task"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "Capture the following commands
1) dsplog -mod FTPD
2) dsplog"

FTPD-7-FTPDLIB2

SEVERITY: In