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

CTC-4-MSGSENDFAILED

Table Of Contents

CTC-4-MSGSENDFAILED

CTC-4-EPIDINSTATEFAIL

CTC-4-MSGALLOCFAILED

CTC-4-APPCRETFAILED

CTC-3-APPSPAWNFAILED

CTC-4-EVTGENRATEFAILE

CTC-4-CDSTCHGREPORTFA

CTC-4-APPSTCHGREPORTF

CTC-4-EVTSENDTOSTMCHN

CTC-4-CTCEVTRGSTRFAIL

CTC-4-MCASTMALLOCERRO

CTC-4-INCORRECTSLOTIN

CTC-4-MEMALLOCFAILED

CTC-4-APPSTCHGRPRTFAI

CTC-4-APPEVTRGSTRFAIL

CTC-4-UNKNOWNEVTRCVD

CTC-4-INCORRECTEVTRCV

CTC-4-UNKNOWNSTATE

CTC-4-INCORRECTDATALE

CTC-4-INVALIDCDST

CTC-4-INVALID_OLD_API

CTC-4-INVALID_NEW_API

CTC-4-FATALERRCALLED

CTC-4-CTC_EPFAILED

CTC-4-CTC_EPATTACH_FA

CTC-4-CTC_INVALID_MSG

CTC-4-CTC_INVALID_MSG

CTC-4-DRV_ACK_SEND_FA

CTC-4-XOVER_ACK_SEND_

CTC-4-SYS_EVENT_FAILE

CTC-4-CTC_SHM_API_FAI

CTC-4-CTC_SHM_EXT_TIM

CTC-4-CTC_INVALID_CD_

CTC-4-CTC_INVALID_CMD

CTC-4-CTC_INVALID_DAT

CTC-4-CTC_SHM_NOTIFY_

CTC-4-CTC_INVALID_LP_

CTC-4-CTC_INVALID_CD_

CTC-4-UNKNOWN_DRV_CMD

CTC-4-INVALID_APPID

CTC-4-NON_LC_APP

CTC-5-TZGETFAILED

CTC-5-TMGETFAILED

CTC-4-TODSETERR

CTC-4-TZSETERR

CTC-4-LCENTRYINUSE

CTC-4-EVTMODEINVALID

CTC-4-LCENTRYNOTSET

CTC-4-ROOTTASKFAILED

CTC-4-EVTEPDCREATFAIL

CTC-4-EVTEPIDATCHFAIL

CTC-4-EVTDELIVERFAIL

CTC-4-APPEVTHDLRFAIL

CTC-4-NONEVTMSGRCVD

CTC-4-NONNULLRCVID

CTC-4-FAILEDAPICALLED

CTC-4-EVENTREGISTERIN

CTC-4-INVALIDAPPNAME

CTC-4-INVALIDEVENT

CTC-4-INVALID_LIFECYC

CTC-4-INVALID_ST_QUAL

CTC-4-MSGBROADCASTFAI

CTC-4-MCAST_RMI_REGIS

CTC-4-MCASTINVALIDDAT

CTC-4-MCASTHDRLENMISM

CTC-5-MCASTUNKNOWNEVT

CTC-4-MCASTEVTLENMISM

CTC-4-MCASTMSGTOOSHOR

CTC-4-MCASTTOOMANYLOS

CTC-5-REXMTPARAMCHG

CTC-4-MCASTEXTRAMSG

CTC-4-MCASTPKTTOO_OLD

CTC-4-MCASTTIMEOUT

CTC-5-MCASTTIMERCANER

CTC-1-MCASTTIMERSCHED

CTC-5-MCASTWARN

CTC-4-MCASTERROR

CTC-4-MCAST_SEQNO_ERR

CTC-4-MCAST_XBAR_SLOT

CTC-4-DRV_ENABLE_FAIL

CTC-4-XOVER_CMD_FAILE

DDTS "ctc"

RAT-4-RATERR001

RAT-4-RATERR002

RAT-5-RATERR003

RAT-4-RATERR004

RAT-4-RATERR005

RAT-4-RATERR006

RAT-4-RATERR007

RAT-4-RATERR008

RAT-4-RATERR009

RAT-7-RATERR010

RAT-5-RATERR011

RAT-5-RATERR012

RAT-7-RATERR013

RAT-5-RATERR014

RAT-5-RATERR015

RAT-7-RATERR016

RAT-4-RATERR017

RAT-5-RATERR018

RAT-5-RATERR019

RAT-4-RATERR020

RAT-5-RATERR021

RAT-5-RATERR022

RAT-5-RATERR023

RAT-5-RATERR024

RAT-7-RATERR025

RAT-7-RATERR026

RAT-5-RATERR027

RAT-5-RATERR028

RAT-5-RATERR029

RAT-5-RATERR030

RAT-5-RATERR031

RAT-5-RATERR032

RAT-4-RATERR033

RAT-5-RATERR034

RAT-7-RATERR035

RAT-7-RATERR036

RAT-5-RATERR037

RAT-5-RATERR038

RAT-5-RATERR039

RAT-5-RATERR040

RAT-5-RATERR041

RAT-5-RATERR042

RAT-5-RATERR043

RAT-5-RATERR044

RAT-5-RATERR045

RAT-5-RATERR046

RAT-4-RATERR047

RAT-5-RATERR048

RAT-5-RATERR049

RAT-5-RATERR050

RAT-5-RATERR051

RAT-5-RATERR052

RAT-5-RATERR053

RAT-5-RATERR054

RAT-5-RATERR055

RAT-5-RATERR056

RAT-5-RATERR057

RAT-5-RATERR058

RAT-5-RATERR059

RAT-4-RATERR060

RAT-5-RATERR061

RAT-5-RATERR062

RAT-4-RATERR063

RAT-5-RATERR064

RAT-5-RATERR065

RAT-7-RATERR066

RAT-7-RATERR067

RAT-5-RATERR068

RAT-5-RATERR069

RAT-5-RATERR070

RAT-5-RATERR071

RAT-5-RATERR072

RAT-5-RATERR073

RAT-5-RATERR074

RAT-5-RATERR075

RAT-7-RATERR076

RAT-5-RATERR077

RAT-7-RATERR078

RAT-7-RATERR079

RAT-5-RATERR080

RAT-5-RATERR081

RAT-5-RATERR082

RAT-5-RATERR083

RAT-4-RATERR084

RAT-4-RATERR085

RAT-4-RATERR086

RAT-5-RATERR087

RAT-5-RATERR088

RAT-5-RATERR089

RAT-5-RATERR090

RAT-5-RATERR091

RAT-7-RATERR092

RAT-7-RATERR093

RAT-5-RATERR094

RAT-5-RATERR095

RAT-7-RATERR096

RAT-5-RATERR097

RAT-5-RATERR098

RAT-5-RATERR099

RAT-5-RATERR100

RAT-5-RATERR101

RAT-5-RATERR102

RAT-7-RATERR103

RAT-5-RATERR104

RAT-5-RATERR105

RAT-5-RATERR106

RAT-5-RATERR107

RAT-5-RATERR108

RAT-5-RATERR109

RAT-5-RATERR110

RAT-4-RATERR112

DDTS "config-upload"

CUTS-7-CUTS_UPDT_DONE

CUTS-7-SEND_CUTV_FAIL

CUTS-7-UPD_FCB_FAIL

CUTS-7-TMR_REINIT_FAIL

CUTS-7-SEMGIVE_FAIL

CUTS-7-CUTS_FILE_MUTEX

CUTS-5-TXID_GET_FAILED

CUTS-7-INV_TXID

CUTS-7-CANNOT_PROCEED

CUTS-7-CUTS_UPDT_FAIL

CUTS-7-RMTCLOSE_FAIL

CUTW-5-INVALID_PARAM

CUTW-5-TXID_GET_FAILED

CUTW-5-TIME_GET_FAILED

CUTW-5-OPEN_FAILED

CUTW-5-FILE_NAME_PARSE

CUTW-5-BITMAP_FAILURE

CUTW-5-ALARM_FILE_PATH

CUTW-5-INVALID_ALARM_F

CUTW-5-ALARM_READ_FAIL

CUTW-5-NULL_ERRHDLR

CUTW-5-FILE_READFAIL

CUTW-5-REMOVE_FAIL

CUTW-7-VLDN_CNTR_EXCEE

CUTW-5-RMT_FILE_IOCTL_

CUTW-5-LATEST_STATIC_F

CUTW-5-ENGINE_INVALID_

CUTW-5-ENGINE_REQ_PROC

CUTW-5-ENGINE_INVALID_

CUTW-5-INVALID_SLOT

CUTW-5-ENGINE_INVALID_

CUTW-5-ENGINE_SEEK_LEN

CUTW-5-REPLICATE_FAIL

CUTW-5-INVALID_REQUEST

CUTW-5-TXID_AUDIT_FAIL

CUTW-5-CHKSUM_FAILURE

CUTW-5-MEM_ALLOC_FAIL

CUTW-5-ALARM_FILE_BUFF

CUTW-5-STBY_REMOVE_FAI

CUTR-5-CUT_RAM_FILE

CUTR-5-CUT_RAM_NAME

CUTR-5-CUT_RAM_LOG

DDTS "config-upload"

CUTS-7-CUTS_DIR_FOUND

CUTS-4-CUTS_NON_DIR_FI

CUTS-4-CUTS_IOCTL_FAIL

CUTS-4-CUTS_OPEN_FAILE

CUTS-5-CUTS_MKDIR_FAIL

CUTS-7-ACK_TIMEOUT

CUTS-4-CUTS_EPID

CUTS-5-CUTS_TIMER_CREA

CUTS-4-CUTS_ATTHDLR

CUTS-5-CUTS_TMR_SCHD

CUTS-5-CUTS_TMR_CNCL

CUTS-4-CUTS_IPC_FREE_E

CUTS-5-IPCFAIL

CUTS-5-IPC_ALLC_FAILED

CUTS-7-CUTS_INVALID_RQ

CUTS-7-CUTS_INVALID_RQ

CUTS-5-CUTS_WRKR_UPDAT

CUTS-7-TMR_ERROR

CUTS-5-RNWY_TASK

CUTS-5-BAD_RSPNSE

CUTS-7-CUTS_FC_FAILED

CUTS-4-BAD_FILEINDX

CUTS-7-FILE_STATE_GENE

CUTS-7-CUTS_CHILD_ACTI

CUTS-7-CUTS_EPID_RESPO

CUTS-7-CUTS_FC_DONE

CUTS-5-CUTS_TRAP_NOTAS

CUTS-7-CUTS_TRAP_START

CUTS-7-CUTS_TRAP_FAIL

CUTS-7-CUTS_TRAP_DONE

CUTS-7-CUTS_TRAP_ABRT

CUTS-7-TRAP_SEND_FAIL

CUTS-7-CUTS_UPDT_FAIL

DDTS "config-upload"

CUTW-4-CUTW_EPID

CUTW-4-CUTW_TIMER_CREA

CUTW-4-CUTW_ATTHDLR

CUTW-5-CUTW_TMR_SCHD

CUTW-5-CUTW_TMR_CNCL

CUTW-4-CUTW_IPC_FREE_E

CUTW-5-IPCFAIL

CUTW-4-IPC_ALLC_FAILED

CUTW-5-CUTW_INVALID_RQ

CUTW-4-CUTW_EPID_RESOL

CUTW-5-CUTW_WRKR_UPDAT

CUTW-4-CUTW_INIT_PTR

CUTW-5-CUTW_FC_FAILED

CUTW-5-BAD_FILEINDX

CUTW-7-CUTWFILENAME

CUTW-7-W_RATEVENTPENDI

CUTW-7-NULL_FILEP

CUTW-7-TASK_STATUS_TRA

CUTW-7-SEMTAKE_FAIL

CUTW-7-SEMGIVE_FAIL

CUTW-7-NULL_PTR

CUTW-5-MEM_FAIL

CUTW-5-MEMDEALL_FAIL

CUTW-5-RTOID_FAIL

CUTW-5-TBLOID_FAIL

CUTW-5-CNFOID_FAIL

CUTW-5-CNFVRBND_FAIL

CUTW-5-FINDOBJ_FAIL

CUTW-7-GTNXT_FAIL

CUTW-5-WRITE_FAIL

CUTW-5-GET_FAIL

CUTW-5-GETNEXT_FAIL

CUTW-5-GETSCLR_FAIL

CUTW-5-IOCTL_FAIL

CUTW-7-CR_RESULT

CUTW-5-FILE_ERR

CUTW-5-WRITE_BYTESFAIL

CUTW-4-MAX_ROWS_EXCEED

DDTS "ccma"

DAL-4-DALERR

DDTS "diskdb"

DB2S-4-DBSVR_RESV_NO_D

DB2S-5-PSEURESV_NO_DB

DB2C-4-DBCLNT_COMEP

DB2C-3-DBCLNT_EPHNDLR

DB2C-4-DBCLNT_TMRERR

DB2C-4-DBCLNT_RETXQ

DB2C-5-DBCLNT_CTCAPI

DB2C-7-DBCLNT_STERR

DB2C-5-DBCLNT_UNEXPEVT

DB2C-3-DBCLNT_VER_NOTS

DB2C-4-DBCLNT_INVEVTGR

DB2C-5-DBCLNT_INVACCES

DB2C-4-DBCLNT_INVMSG

DB2C-5-DBCLNT_UNAVL

DB2C-4-DBCLNT_RECVMSG

DB2C-5-DBCLNT_RETXFAIL

DB2C-5-DBCLNT_SENDFAIL

DB2C-5-DBCLNT_REPLYFAI

DB2C-5-DBCLNT_MSGALLOC

DB2C-6-DBCLNT_TXCLEANU

DB2C-5-DBCLNT_RESPTMOU

DB2C-5-DBCLNT_MAXEXCEE

DB2C-5-DBCLNT_NOFREEID

DB2C-5-DB2CLNT_INVAPPI

DB2C-5-DBCLNT_INVTXID

DB2C-5-DBCLNT_TXMSG

DB2C-5-DBCLNT_OUTOFRAN

DB2C-5-DBCLNT_NOTOWNER

DB2C-5-DBCLNT_IDNONEXI

DB2C-4-DBCLNT_INFOERR

DB2C-6-DBCLNT_UNREG

DB2C-5-DBCLNT_NONREDUP

DB2C-5-DBCLNT_INTERNAL

DB2C-5-DBCLNT_INVSVRRE

DB2C-4-DBCLNT_INVSVRRE

DB2C-4-DBCLNT_INVSVRRE

DB2C-4-DBCLNT_INVPEERR

DB2C-4-DBCLNT_INVPEERR

DB2C-5-DBCLNT_DUPREQ

DB2C-5-DBCLNT_BAD_SWID

DB2C-4-DBCLNT_SPAWN_ER

DB2C-4-DBCLNT_MEM_ERR

DB2C-4-DBCLNT_CONV_OP_

DB2C-5-UPGFAIL

DB2C-1-TASKSPAWN

DB2C-5-TBLINFCOR

DB2C-5-RECNACK

DB2C-5-INVRECRESP

DB2C-7-STBAVAIL

DB2C-5-REGSTSNACK

DB2C-7-REG

DDTS "diskdb"

DB2S-4-DBSVR_COMEP

DB2S-3-DBSVR_TASK_SPAW

DB2S-5-DBSVR_SEM_FAIL

DB2S-4-DBSVR_EPHNDLR

DB2S-5-DBSVR_MEM_FAIL

DB2S-4-DBSVR_SHMAPI

DB2S-5-DBSVR_IPC_FAIL

DB2S-4-DBSVR_DOS_FAIL

DB2S-7-DIRDELETE

DB2S-4-DBSVR_RECVMSG

DB2S-5-DBSVR_GEN_FAIL

DB2S-4-DBSVR_INVEVTGRP

DB2S-4-DBSVR_VER_NOTSU

DB2S-5-DBSVR_CTCAPI

DB2S-6-PSEURESV

DB2S-4-EVTPROCFAIL

DB2S-4-DBSVR_BAD_DATA

DB2S-4-DBSVR_BAD_REC

DB2S-5-DBSVR_VAL_FAIL

DB2S-5-DBSVR_OS_FAIL

DB2S-4-DBSVR_INTERNAL_

DB2S-5-DBSVR_GEN_FAIL1

DB2S-5-DBSVR_GEN_FAIL2

DB2S-5-DBSVR_GEN_FAIL3

DB2S-5-DBSVR_WARNING

DB2S-4-DBSVR_BAD_PARAM

DB2S-7-DBSVR_BAD_SWID

DB2S-7-SKIPCHK

DB2S-7-SKIPSLOT

DB2S-7-CHKCOMP

DB2S-5-INVLSLOT

DB2S-5-DBSVR_INVROLE

DB2S-5-INVPARAM

DB2S-7-DBVERDEL

DB2S-7-CDINSRECD

DB2S-7-INFOREC

DB2S-5-DBSVR_UNEXPEVT

DB2S-7-CTCEVTRECD

DB2S-7-LSLOTINFO

DB2S-4-INVCTCINFO

DB2S-4-INVCTCSLOT

DB2S-5-CTCEVTMIS

DB2S-5-UPDLOST

DB2S-5-INVREQ

DB2S-7-STBAVAIL

DB2S-7-STBNOTAVAIL

DB2S-7-REGSTBAVAIL

DB2S-7-REG

DB2S-7-TBLNOTRDY

DB2S-4-PEERCDSTFAIL

DB2S-7-REDEVT

DB2S-2-FILELOCK_FAIL

DB2S-7-SIG_FILE

DB2S-7-ALTERLOG

UPDN-7-DBUPDATE

DDTS "diskdb"

DB2S-4-DBSYNC_COMEP

DB2S-4-DBSYNC_TMRERR

DB2S-4-DBSYNC_RETXQ

DB2S-5-DBSYNC_CTCAPI

DB2S-4-DBSYNC_FILE_LOC

DB2S-4-DBSYNC_SHMAPI

DB2S-7-SHMINFO

DB2S-4-DBSYNC_DATAXFER

DB2S-5-DBSYNC_INVMSGTY

DB2S-5-DBSYNC_INVMSGLG

DB2S-5-DBSYNC_HDRVAL

DB2S-5-DBSYNC_HDRVALMM

DB2S-5-DBSYNC_INVRESPI

DB2S-5-DBSYNC_LENVAL

DB2S-5-DBSYNC_INVVAL

DB2S-5-DBSYNC_NULLPARA

DB2S-5-DBSYNC_INVLVAL

DB2S-5-DBSYNC_INSUF_BU


CTC-4-MSGSENDFAILED

SEVERITY: Error
FORMAT: "%s Failed to send message to epid 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to send message to the specified End Point Id"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-EPIDINSTATEFAIL

SEVERITY: Error
FORMAT: "%s Failed to instantiate CTC epid"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to instantiate the specified End Point Id"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MSGALLOCFAILED

SEVERITY: Error
FORMAT: "%s Failed to allocate message "
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to allocate message"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-APPCRETFAILED

SEVERITY: Error
FORMAT: "%s Failed to create application AppId %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to create application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-3-APPSPAWNFAILED

SEVERITY: Minor Alert
FORMAT: "%s Failed to spawn application AppId %x"
FLAG: Stack Trace|Write to Bram
THROTTLING: One Tick
EXPLANATION: "CTC has failed to properly spawn an app"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-EVTGENRATEFAILE

SEVERITY: Error
FORMAT: "%s%d Event Generate Api failed for event %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "EventGenerate APi failed for an event"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-CDSTCHGREPORTFA

SEVERITY: Error
FORMAT: "%s Failed to send CD_ST change message to SHM "
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to send the Card State Change message to SHM"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-APPSTCHGREPORTF

SEVERITY: Error
FORMAT: "%s App Id 0x%x Failed to report APP_ST change to CTC"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to report/send Application State Change message to CTC"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-EVTSENDTOSTMCHN

SEVERITY: Error
FORMAT: "%s Failed to send 0x%x event to CTC state Machine"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to send the specified event to CTC SM"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-CTCEVTRGSTRFAIL

SEVERITY: Error
FORMAT: "%s CTC failed to register with SHM for events"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "CTC failed to register with SHM for events"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCASTMALLOCERRO

SEVERITY: Error
FORMAT: "%s CTC counter error %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "CTC encounter a malloc related 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: No Required Info

CTC-4-INCORRECTSLOTIN

SEVERITY: Error
FORMAT: "%s Incorrect/invalid information received"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Invalid information is received"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MEMALLOCFAILED

SEVERITY: Error
FORMAT: "%s Failed to allocate memory"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Memory allocation 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: No Required Info

CTC-4-APPSTCHGRPRTFAI

SEVERITY: Error
FORMAT: "%s APP Id- 0x%x failed to report state change"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Application failed to report a state change transition"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-APPEVTRGSTRFAIL

SEVERITY: Error
FORMAT: "%s App Id- 0x%x failed to register for CTC events"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Application failed to register for CTC events"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-UNKNOWNEVTRCVD

SEVERITY: Error
FORMAT: "%s UnKnown event/msg received"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Unknown Event message is received"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INCORRECTEVTRCV

SEVERITY: Error
FORMAT: "%s Unexpected event/msg received from app Id- 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Unexpected Event message received from Application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-UNKNOWNSTATE

SEVERITY: Error
FORMAT: "%s App Id- 0x%x has Unknown/Invalid state"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Application had an invalid state"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INCORRECTDATALE

SEVERITY: Error
FORMAT: "%s parameter %s has Unknown/Invalid length"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Parameter has invalid length"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INVALIDCDST

SEVERITY: Error
FORMAT: "%s The card state %d is Unknown/Invalid"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Card state is invalid"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INVALID_OLD_API

SEVERITY: Error
FORMAT: "%s An old model API called by a new model app (AppId 0x%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "API called by the application is not allowed"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INVALID_NEW_API

SEVERITY: Error
FORMAT: "%s A new model API called by a old model app (AppId 0x%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "API called by the application is not allowed"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-FATALERRCALLED

SEVERITY: Error
FORMAT: "%s An App with Appid 0x%x invoked the fatalerror API with errno 0x%x \n"
FLAG: Stack Trace | Write to Bram
THROTTLING: One Tick
EXPLANATION: "Application reported FATAL 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: No Required Info

CTC-4-CTC_EPFAILED

SEVERITY: Error
FORMAT: "%s CTC Communications Endpoint FAILED (errno 0x%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "CTC Communications Endpoint 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: No Required Info

CTC-4-CTC_EPATTACH_FA

SEVERITY: Error
FORMAT: "%s CTC Com EP attach failed epid 0x%x (errno 0x%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "CTC Communications Endpoint attach/bind 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: No Required Info

CTC-4-CTC_INVALID_MSG

SEVERITY: Error
FORMAT: "%s Invalid message received"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An invalid message is received"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-CTC_INVALID_MSG

SEVERITY: Error
FORMAT: "%s CTC Invalid message data received"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Invalid CTC messae data is received"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-DRV_ACK_SEND_FA

SEVERITY: Error
FORMAT: "%s%d Failed to send drv cmds ack back to SHM"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to send drv cmds ack back to SHM"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-XOVER_ACK_SEND_

SEVERITY: Error
FORMAT: "%s%d Failed to send Xover cmds ack back to SHM"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to send Xover cmds ack back to SHM"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-SYS_EVENT_FAILE

SEVERITY: Error
FORMAT: "%s System event send failed, event = %d, errno=0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Could not send a CTC System Event"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-CTC_SHM_API_FAI

SEVERITY: Error
FORMAT: "%s %s() failed, errno = 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The Shelf Manager API call 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: No Required Info

CTC-4-CTC_SHM_EXT_TIM

SEVERITY: Error
FORMAT: "%s %s() failed, errno = 0x%x, errCode = 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The Shelf Manager API call 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: No Required Info

CTC-4-CTC_INVALID_CD_

SEVERITY: Error
FORMAT: "%s Received an invalid card state (0x%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An invalid card state is received"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-CTC_INVALID_CMD

SEVERITY: Error
FORMAT: "%s Received invalid command length actual 0x%x, expected 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An invalid command length is received"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-CTC_INVALID_DAT

SEVERITY: Error
FORMAT: "%s SHM Data Inconsistency %s = 0x%x, expected = 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Invalid data"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-CTC_SHM_NOTIFY_

SEVERITY: Error
FORMAT: "%s SHM state change notification failed (%d), errno=0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "SHM state change notification 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: No Required Info

CTC-4-CTC_INVALID_LP_

SEVERITY: Error
FORMAT: "%s Invalid local port message reveived (%s = 0x%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An invalid local port message is received"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-CTC_INVALID_CD_

SEVERITY: Error
FORMAT: "%s Invalid card type received from SHM %d (0x%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An invalid card type is received from SHM"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-UNKNOWN_DRV_CMD

SEVERITY: Error
FORMAT: "%s%d An unknown/unidentified drv. cmd was received "
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An unknown drv cmd was received at the CTC"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INVALID_APPID

SEVERITY: Error
FORMAT: "%s%d the calling application has invalid Appid (0x%x) "
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "the calling application has invalid Appid"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-NON_LC_APP

SEVERITY: Error
FORMAT: "%s%d the calling application is non-LC compliant "
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "the calling application is non-LC compliant"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-5-TZGETFAILED

SEVERITY: Warning
FORMAT: "%s%d CTC failed to get Timezone info from ssi"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "ssiTimeZoneGet value returned ERROR to CTC"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CTC-5-TMGETFAILED

SEVERITY: Warning
FORMAT: "%s%d CTC failed to get TimeofDay info from ssi"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "ssiTimeofDayGet value returned ERROR to CTC"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CTC-4-TODSETERR

SEVERITY: Error
FORMAT: "%s%d Could not set timeofday"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "ssiTimeOfDaySet returned an 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: No Required Info

CTC-4-TZSETERR

SEVERITY: Error
FORMAT: "%s%d Could not set timezone"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "ssiTimeZoneSet returned an 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: No Required Info

CTC-4-LCENTRYINUSE

SEVERITY: Error
FORMAT: "%s LC Table entry %x already in use"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "LC table entry is already in use"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-EVTMODEINVALID

SEVERITY: Error
FORMAT: "%s Event mode %x invalid for appId %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The event mode is invalid for the Application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-LCENTRYNOTSET

SEVERITY: Error
FORMAT: "%s control parms not set for LC Table entry %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The control parameters are not set for the specified LS table entry"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info
CTC-4-ROOTSKCREATFAIL
SEVERITY: Error
FORMAT: "Failed to create app root task, appid %x, rc %x, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to create the Application's root 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: No Required Info

CTC-4-ROOTTASKFAILED

SEVERITY: Error
FORMAT: "App root task failed, appid %x, rc %x, errno %x"
FLAG: Stack Trace | Write to Bram
THROTTLING: One Tick
EXPLANATION: "Application's root task 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: No Required Info

CTC-4-EVTEPDCREATFAIL

SEVERITY: Error
FORMAT: "Failed to create evt rcvr epid, appid %x, rc %x, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to create Event receiver end point Id for the Application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-EVTEPIDATCHFAIL

SEVERITY: Error
FORMAT: "Failed to attach handler to evt rcvr epid 0x%x, appid %x, handler %x, rc %x, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to attach Event handler to the event receiver end point Id for the Application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-EVTDELIVERFAIL

SEVERITY: Error
FORMAT: "%s Failed to deliver evt %x to app %x, evtLen %d, rc %x, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to send Event to an Application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-APPEVTHDLRFAIL

SEVERITY: Error
FORMAT: "%s App evt hdlr failed, evt %x, app %x, evtLen %d, rc %x, errno %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Application's event handler 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: No Required Info

CTC-4-NONEVTMSGRCVD

SEVERITY: Error
FORMAT: "Non-event message %x received, app %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "A Non-Event message is received"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-NONNULLRCVID

SEVERITY: Error
FORMAT: "Unable to process sync message, app %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Unable to process sync message for the Application"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-FAILEDAPICALLED

SEVERITY: Error
FORMAT: "%s%d Failed API call by AppId 0x%x"
FLAG: Stack Trace | Write to Bram
THROTTLING: One Tick
EXPLANATION: "An application failed to transition to next state"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-EVENTREGISTERIN

SEVERITY: Error
FORMAT: "Event is registered for different appId, current appid %x, request appid %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "A request to register for a card event was made by a different appId than the one currently registered."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INVALIDAPPNAME

SEVERITY: Error
FORMAT: "Invalid App Name %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An invalid App name was passed in"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INVALIDEVENT

SEVERITY: Error
FORMAT: "%s%d Invalid event was passed %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An invalid event was passed in"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-INVALID_LIFECYC

SEVERITY: Error
FORMAT: "%s%d Can't register/unregister mandatory life-cycle events (%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An mandatory life-cycle event was specified"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info
CTC-4-CD_EVT_REGIS_FA
SEVERITY: Error
FORMAT: "%s%d card event registration for event %x failed"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: " card event registration for a given event 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: No Required Info

CTC-4-INVALID_ST_QUAL

SEVERITY: Error
FORMAT: "%s%d An event with invalid state qualifier %d was received"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "An event with invalid state qualiifer was received at CTC"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MSGBROADCASTFAI

SEVERITY: Error
FORMAT: "%s Failed to send message to %s epid 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Failed to send message to an End point Id"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCAST_RMI_REGIS

SEVERITY: Error
FORMAT: "%s%d Failed to register MCAST port with RMI"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "CTC failed to register mcast event receive port with RMI "
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCASTINVALIDDAT

SEVERITY: Error
FORMAT: "%sInvalid %s %d. Must be %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast receiver received a multicast message on a invalid port or the message had a wrong version number on it"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCASTHDRLENMISM

SEVERITY: Error
FORMAT: "%sMessage Seq No %d Message Len %d, Header Len %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Multicast receiver received a messge in which the length of the message was less than the Multicast protocol header length"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-5-MCASTUNKNOWNEVT

SEVERITY: Warning
FORMAT: "%sMessage Seq No %d Unknown Event 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Multicast receiver received a message in which there was an event that could not be recognized by the receiver"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CTC-4-MCASTEVTLENMISM

SEVERITY: Error
FORMAT: "%sMessage Seq No %d Event 0x%x is of length %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast receiver received a message in which an event length did not match the length expectd by the receiver"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCASTMSGTOOSHOR

SEVERITY: Error
FORMAT: "%sMessage Seq No %d Message length %d too short at event 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Multicast receiver received a message which was too short to hold all the events in the message"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCASTTOOMANYLOS

SEVERITY: Error
FORMAT: "%s Message Seq No %d Too many messages missed. Last seen seq no %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast receiver missed too many messages in between the current one and the previous one"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-5-REXMTPARAMCHG

SEVERITY: Warning
FORMAT: "%s%d - Rexmission parameters changed rexmtCount %d, rexmitInt %d "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Rexmission parameters are changed from old values to New set of parameters"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CTC-4-MCASTEXTRAMSG

SEVERITY: Error
FORMAT: "%s Received extra packet received seqNo %d, prevSeqNo %d, NewSeqNo count %d "
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Mcast Receiver Received extra packets before newseqCount changes "
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCASTPKTTOO_OLD

SEVERITY: Error
FORMAT: "%sMessage Seq No %d Pkt received is old. Last seen seq no %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast receiver has received pkt which is much older or previous than the last seen"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCASTTIMEOUT

SEVERITY: Error
FORMAT: "%sLast Message Seq No %d rexmt count %d rexmt interval %d Time out %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast receiver did not get any messages before the timeout period"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-5-MCASTTIMERCANER

SEVERITY: Warning
FORMAT: "%sCould not Cancel Timeout previously set"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Multicast receiver could not cancel the timeout"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CTC-1-MCASTTIMERSCHED

SEVERITY: Fatal
FORMAT: "%sCould not schedule timeout"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast receiver could not schedule a timeout"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-5-MCASTWARN

SEVERITY: Warning
FORMAT: "%sWARNING %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast receiver issued a warning"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CTC-4-MCASTERROR

SEVERITY: Error
FORMAT: "%sERROR %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast receiver encountered an 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: No Required Info

CTC-4-MCAST_SEQNO_ERR

SEVERITY: Error
FORMAT: "Multi-cast events may have been lost on slot %d, got 0x%x (expected 0x%x)"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Multicast events may have been lost during switch-over"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-MCAST_XBAR_SLOT

SEVERITY: Error
FORMAT: "Xbar Slots expected = %d, received = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Multicast message from Xbar exceeding bounds."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: No Required Info

CTC-4-DRV_ENABLE_FAIL

SEVERITY: Error
FORMAT: "%s:%d Failed to enable drivers %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "CTC failed to enable drivers which have been registered by the applications "
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

CTC-4-XOVER_CMD_FAILE

SEVERITY: Error
FORMAT: "%s:%d Failed to process Xover cmd %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "CTC failed to process xover cmd"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

DDTS "ctc"

RAT-4-RATERR001

SEVERITY: Error
FORMAT: "RAT Exception Handler() called for \"%s\", exception 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT has received an unexpected exception and the parameter passed in is not valid"
RECOMMENDED ACTION: Reset the card. If the problem 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: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-4-RATERR002

SEVERITY: Error
FORMAT: "RAT Exception Handler ssiFree() failed for \"%s\", addr 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The memory free failed during the exception handler."
RECOMMENDED ACTION: Reset the card. If the problem 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: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-5-RATERR003

SEVERITY: Warning
FORMAT: "Event received for \"%s\" but current event status is \"%s\"."
FLAG: No Flag
THROTTLING: Hundred Milliseconds
EXPLANATION: "The RAT has received an event while processing another event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR004

SEVERITY: Error
FORMAT: "Interactive Task death occurred in \"%s\" system, task \"%s\" (%d) "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "An interactive child task has abnormally ended."
RECOMMENDED ACTION: Reset the card. If the problem 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: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-4-RATERR005

SEVERITY: Error
FORMAT: "Callback Task death occured in \"%s\" system, task \"%s\" (%d) "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "A callback child task has abnormally ended."
RECOMMENDED ACTION: Reset the card. If the problem 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: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-4-RATERR006

SEVERITY: Error
FORMAT: "ssiIpcMessageFree(pMblk = 0x%08X) failed, result was 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "An ssiIpcMessageFree failed when it should not have. Potential memory leak"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-4-RATERR007

SEVERITY: Error
FORMAT: "RAT subsystem \"%s\" ssiIpcMessageAllocate (size %d) failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "An ssiIpcMessageAllocate failed when it should not have."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-4-RATERR008

SEVERITY: Error
FORMAT: "Rat \"%s\" ssiIpcMessageSend(Epid 0x%08X, pMblk 0x%08X) result 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "An ssiIpcMessageSend failed when it should not have."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-4-RATERR009

SEVERITY: Error
FORMAT: "Role change attempt invalid at end of event handler, status = \"%s\" (%d)"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT has detected an invalid state at the end of the event handler logic. This is most likely due to a logic failure with the RAT"
RECOMMENDED ACTION: Reset the card. If the problem 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: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-7-RATERR010

SEVERITY: Information
FORMAT: "Subsystem \"%s\", Interactive child task has abnormally ended. <taskName,taskId> = <\"%s\",%d>"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Interactive child task has abnormally ended."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR011

SEVERITY: Warning
FORMAT: "Invalid start mode \"%s\" (%d) passed to ratMain."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Unexpected start up mode"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR012

SEVERITY: Warning
FORMAT: "ssiTaskInitAck failed, result is 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "This Task is trying to acknowledge the task spawner the initialization status of the task. However, an error has occur, this task might die resulting from the error."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR013

SEVERITY: Information
FORMAT: "rat_init() failed. Cardrole = \"%s\" (%d), status = \"%s\" (%d)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "This task(RAT) failed to initialize it structure."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR014

SEVERITY: Warning
FORMAT: "An overall timeout occurred for \"%s\" RAT tasks."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "A RAT timeout results when one or more children takes longer to perform a state change request than is allocated for the effort."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR015

SEVERITY: Warning
FORMAT: "Subsystem \"%s\", Can not attach handler. <task,id,epid,result> = <\"%s\", %d, 0x%08X, %d>."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT could not attach the handler function to the communications endpoint."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR016

SEVERITY: Information
FORMAT: "\"%s\" RAT, task \"%s\" (%d) completes \"%s\" (%d) request."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "This task has successfully processed the request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR017

SEVERITY: Error
FORMAT: "The \"%s\" subsytem RAT died, return code 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task has died or no longer in service"
RECOMMENDED ACTION: Reset the card. If the problem 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: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-5-RATERR018

SEVERITY: Warning
FORMAT: "Subsystem \"%s\", RAT role change timeout occured for child task Id %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Task timer expires before the task has completed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR019

SEVERITY: Warning
FORMAT: "RAT timeout occurred for task %d when state was \"%s\" (%d)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "An timeout event has occur where it shouldn't have been"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR020

SEVERITY: Error
FORMAT: "Invalid child id passed from child to RAT subsystem \"%s\", offset = %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Somehow the child passed us an invalid offset."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-5-RATERR021

SEVERITY: Warning
FORMAT: "Can not allocate resource, size = %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to allocate resource for this task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR022

SEVERITY: Warning
FORMAT: "ssiSynchTimerCreate() failed , result = %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to create synchronous timer for this task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR023

SEVERITY: Warning
FORMAT: "Subsystem \"%s\", IPC end point create failed. <task,offset,epid> = <\"%s\", %d, 0x%08X>"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to create IPC communication end point."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR024

SEVERITY: Warning
FORMAT: "ssiIpcComEpNameBind() subsys \"%s\" task \"%s\" (%d) rc= 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR025

SEVERITY: Information
FORMAT: "rat_init_attempt() exited, result = %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Stepping out of init function with invalid state"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR026

SEVERITY: Information
FORMAT: "rat_children_init() exited, state \"%s\" (%d), intrActvTskCnt %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Task is not successfully initialized. This can result in the death of the task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR027

SEVERITY: Warning
FORMAT: "Discovered child (offset %d) with illegal state \"%s\" %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task will die because the child's state is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR028

SEVERITY: Warning
FORMAT: "Subsystem \"%s\", task spawn failed. <taskname,offset> = <\"%s\",%d> "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Task spawn failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR029

SEVERITY: Warning
FORMAT: "RAT subsystem \"%s\", child task has not acknowledge. <task name, offset, status> = <\"%s\", %d, 0x%08X >."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Spawned task failed to acknowledge. This task will die."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR030

SEVERITY: Warning
FORMAT: "Ack for RAT \"%s\", task \"%s\" (%d) with unexpected status \"%s\" (0x%08X)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task receive ACK from it child but it child's status is not in processing mode. This will result in child's status to set to fail."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR031

SEVERITY: Warning
FORMAT: "RAT \"%s\" task offset (%d) exceeds range (%d)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Timeout event receive from a child outside the range of the table"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR032

SEVERITY: Warning
FORMAT: "RAT can not find taskid %d in child table."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task received a message from it children but it can't find a matching taskId from it child table "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR033

SEVERITY: Error
FORMAT: "RAT \"%s\" taskId mismatch taskId 0x%08X, msgtaskId 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Task ID that was send from RAT is not match with current task id"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-5-RATERR034

SEVERITY: Warning
FORMAT: "RAT \"%s\", Unexpected response from child. <taskName,taskId, responseMsg,response> = <\"%s\", %d, \"%s\", %d>"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Unexpected response from child. Task will exit."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR035

SEVERITY: Information
FORMAT: "\"%s\" RAT, task \"%s\" (%d) started successfully."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "A regression test task has begun properly."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR036

SEVERITY: Information
FORMAT: "RAT \"%s\" task \"%s\", offset %d pending on \"%s\" (%d) request."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "A regression test task is waiting on a previous request."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR037

SEVERITY: Warning
FORMAT: "ratRoleChange() entered for \"%s\", status \"%s\" (%d) invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task can not change role because it got invalid status"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR038

SEVERITY: Warning
FORMAT: "ratRoleChange() entered for \"%s\", request \"%s\" (%d) invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task can not change role because it got invalid request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR039

SEVERITY: Warning
FORMAT: "ratRoleChange() failed for \"%s\", request \"%s\" (%d) invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Can not transition to new state. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR040

SEVERITY: Warning
FORMAT: "RAT \"%s\", task \"%s\" (%d) state \"%s\" (%d) invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task can not change role because it got invalid state"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR041

SEVERITY: Warning
FORMAT: "ssiIpcMessageAllocate(%d) failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR042

SEVERITY: Warning
FORMAT: "ssiIpcMessageSend(epid 0x%08X, pMblk 0x%08X) failed, result %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR043

SEVERITY: Warning
FORMAT: "State request (%d, \"%s\") corrupted during rat_child_roleChange."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Unknow CTC state receive by RAT."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR044

SEVERITY: Warning
FORMAT: "ssiScheduleTimeout() failed for child \"%s\", offset %d, result %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task is trying to schedules a timeout event for each spawned child and it failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR045

SEVERITY: Warning
FORMAT: "ssiScheduleTimeout(%d) failed for overall timer, result %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task is trying to create a timeout event and it failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR046

SEVERITY: Warning
FORMAT: "User supplied callback (0x%08X) when passed \"%s\" did not return OK."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "User supplied function was called but return not OK"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR047

SEVERITY: Error
FORMAT: "rat_child_roleChange exit reached but state (\"%s\") is invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task is in an invalid state"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-5-RATERR048

SEVERITY: Warning
FORMAT: "ctcApplGotoDbSyncState() failed, result %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR049

SEVERITY: Warning
FORMAT: "Role change failed invalid state combination."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR050

SEVERITY: Warning
FORMAT: "ctcApplGotoRdyState() failed, result %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR051

SEVERITY: Warning
FORMAT: "Role change failed invalid state combination."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR052

SEVERITY: Warning
FORMAT: "ctcApplGotoRdyState() failed, result %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR053

SEVERITY: Warning
FORMAT: "Role change failed invalid state combination."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR054

SEVERITY: Warning
FORMAT: "Invalid Child Id."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task received message from unknown source"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR055

SEVERITY: Warning
FORMAT: "Message from child (offset %d) but role change attempt was \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR056

SEVERITY: Warning
FORMAT: "Received unexpected message from child (offset = %d)"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "We shouldn't receive a message from a task where there aren't any outstanding requests"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR057

SEVERITY: Warning
FORMAT: "Invalid state!!! offset = %d, state = (\"%s\")."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The state of the child entry is invalid. Task failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR058

SEVERITY: Warning
FORMAT: "Unexpected response received from child task. offset = %d, expected resp = \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Unexpected response received from child task. The response should be OK"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR059

SEVERITY: Warning
FORMAT: "ssiTimeoutCancel(), Can not cancel timeout timer for offset %d, result %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Can not cancel timeout timer for child task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR060

SEVERITY: Error
FORMAT: "ssiIpcMessageFree(), Can not free message for offset %d, result %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Can not free memory. This can result in potential memory leak"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-5-RATERR061

SEVERITY: Warning
FORMAT: "ssiTimeoutCancel(), Can not cancel overall timer, result %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Cancellation of timer failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR062

SEVERITY: Warning
FORMAT: "Role change attempt to \"%s\" results in \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to transition to new state."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR063

SEVERITY: Error
FORMAT: "at end of rat_comEpWait_msgHdlr() state (\"%s\") is invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task is not successfully transition to new state"
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-5-RATERR064

SEVERITY: Warning
FORMAT: "Event contains invalid physical slot number %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR065

SEVERITY: Warning
FORMAT: "Event Type 0x%0X ignored, not applicable."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR066

SEVERITY: Information
FORMAT: "Exiting ssiEpComWaitLoop() via ssiMsgWaitExit(ERROR)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task is not successfully transition to new state"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR067

SEVERITY: Information
FORMAT: "Task \"%s\" specifies invalid priority %d, reset to %d, RAT is %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The user data tables for this task contain a priority setting that is not within the permissible range. The RAT reset the priority to an allowable value."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR068

SEVERITY: Warning
FORMAT: "RAT failed going to non provisioning"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT was unable to transition to the non provisioning state. This could be due to a child task problem or logic failure within the RAT itself."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR069

SEVERITY: Warning
FORMAT: "RAT child failed to acknowledge a PXM switchover"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "A RAT child was failed to provide an acknowledgment of a PXM switchover. This is probably due to a child task problem."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR070

SEVERITY: Warning
FORMAT: "\"%s, A RAT child timeout was received for a child (%d) that does not exist"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "A RAT child timeout results when a state change request takes longer than is allocated for that child's state change effort. Normally this would be due to a child task taking too long, but in this case there was no outstanding request."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR071

SEVERITY: Warning
FORMAT: "RAT Child User Data table NULL."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT Child User Data table contains an entry for which the pointer is NULL. This entry should point at a user data structure. This is mostly due to a structure initialization error on the part of the developer, check that the user data field is properly initialized."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR072

SEVERITY: Warning
FORMAT: "RAT Child User Data table entry 0 taskname is invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT Child User Data table should always contain a special entry at the beginning of the table that is properly initialized to indicate the start of the table. This first entrys task name should be set to a default value. See the ctc_rat_example.c code for further details."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR073

SEVERITY: Warning
FORMAT: "Could not allocate enough space (%d bytes) for global epid name."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT attempted to allocate space to build the global epid name and the malloc failed. Most likely this indicates a resource allocation problem or possibly a memory leak."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR074

SEVERITY: Warning
FORMAT: "New Card Role (0x%08X) passed to RAT was invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT was passed an invalid card role value by the CTC during initialization. This could indicate a possible stack corruption or perhaps a change in the CTC protocol that has not been reflected in the RAT."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR075

SEVERITY: Warning
FORMAT: "Can not find a valid offset into the RAT entries base on the TaskId(0x%08X), pRat 0x%08X) returns %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The conversion routine did not find an appropriate matching child in the table."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR076

SEVERITY: Information
FORMAT: "\"%s\" RAT, task \"%s\" (%d) pending \"%s\" (%d) completion."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The regression test task has been notified and the state change function is waiting for the task to update the appropriate flags."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR077

SEVERITY: Warning
FORMAT: "ssiIpcComEpNameResolve(name \"%s\", slot %d) for task \"%s\" returns 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The ssiIpcComEpNameResolve() function failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR078

SEVERITY: Information
FORMAT: "\"%s\" RAT, task \"%s\" (%d) about to request \"%s\" (%d)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The regression test function (by updating the appropriate flags) is about to request that the regression test task change states."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR079

SEVERITY: Information
FORMAT: "ctcApplGotoDbBuildState(0) failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Event explanation comes at later point"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR080

SEVERITY: Warning
FORMAT: "RAT user data table corrupted. <RAT entries, min,max> = <%d, %d, %d>"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The number of entries within the user data table is not in range"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR081

SEVERITY: Warning
FORMAT: "Task \"%s\" (offset %d) info and/or priority invalid at initialization."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The user data tables have NULL pointers for either the task info table or the priority table for this task."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR082

SEVERITY: Warning
FORMAT: "Callback Regression Task (offset %d) RAT_INFO invalid. pRat = 0x%08X"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT_INFO or user data tables have NULL pointers."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR083

SEVERITY: Warning
FORMAT: "Callback Regression Task \"%s\" (offset %d, pRat 0x%08X) data NULL."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The callback structure pointer is NULL."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR084

SEVERITY: Error
FORMAT: "Corrupted msg from RAT \"%s\", task \"%s\" (%d), cookie = 0x%08X)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "A message was received whose magic cookie 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. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-4-RATERR085

SEVERITY: Error
FORMAT: "A RAT was started but passed a NULL pointer to the RAT INFO Structure."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The rat Info Structure pointer is NULL."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-4-RATERR086

SEVERITY: Error
FORMAT: "An invalid pointer (0x%08X) or corrupted RAT_INFO_STRUCT was detected."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The rat Info Structure pointer and/or data is bad."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

RAT-5-RATERR087

SEVERITY: Warning
FORMAT: "Invalid birth state (\"%s\" 0x%08X) detected for task \"%s\" offset %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The rat Info Structure pointer and/or data is bad."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR088

SEVERITY: Warning
FORMAT: "Invalid handler assignments (I=0x%08X, C=0x%08X) for \"%s\" offset %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The rat Info Structure pointer and/or data is bad."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR089

SEVERITY: Warning
FORMAT: "Invalid event list (element %d @ 0x%08X) for task \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The rat Info Structure pointer and/or data is bad."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR090

SEVERITY: Warning
FORMAT: "Invalid event list terminator (element %d @ 0x%08X) for task \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The rat Info Structure pointer and/or data is bad."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR091

SEVERITY: Warning
FORMAT: "RAT Child \"%s\" offset %d specified App2App events but pointer is null."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The user specified the eventFlag bit mask to tell the RAT that there exists an application to application event list for this child but the pointer to this table was null."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR092

SEVERITY: Information
FORMAT: "\"%s\" RAT, task \"%s\" (%d) spawned succesfully with priority %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The user specified task was spawned without issue."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR093

SEVERITY: Information
FORMAT: "RAT subsystem \"%s\" successfully transitioned to new state \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "All members of the RAT group and the RAT have correctly transitioned to the new state."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR094

SEVERITY: Warning
FORMAT: "RAT \"%s\" received illegal state change actionFlag \"%s\" (0x%08X)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "An illegal value was passed to the state change routine."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR095

SEVERITY: Warning
FORMAT: "ratChildResponseMsgHdlr(pRat 0x%08X) called but pMblk NULL."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Function called with invalid parameters."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR096

SEVERITY: Information
FORMAT: "Task has successfully processed the event. \"%s\", \"%s\" (%d) \"%s\" (%d) done, event 0x%08X (@ 0x%08X) len %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Task has successfully processed the event"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR097

SEVERITY: Warning
FORMAT: "RAT detected invalid child ID by subsystem \"%s\" (offset %d)!"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "An invalid offset was passed to one of the generic, reentrant RAT routines. Probably PEBCAK."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR098

SEVERITY: Warning
FORMAT: "Failed registering event (element %d @ 0x%08X) for \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT was unable to register for the specified event."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR099

SEVERITY: Warning
FORMAT: "ratProcessEvent() entered for \"%s\", status \"%s\" (%d) invalid."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The current state is invalid"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR100

SEVERITY: Warning
FORMAT: "ratRoleChange() entered for \"%s\" but acknowledgements (%d) not zero."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "We are attempting a role change but there are already outstanding acknowledgments from a previous request. This is an invalid state and probably indicates either a lost IPC message or a logic error."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR101

SEVERITY: Warning
FORMAT: "\"%s\" RAT, task \"%s\" (%d) epid create timed out during initialization."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The interactive task exceeded the amount of time allotted by the user to establish an epid through which it could receive RAT events. Is the initTickLimit value specified by the user's data structure too small?"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR102

SEVERITY: Warning
FORMAT: "RAT \"%s\", task \"%s\" (%d) recv'd invalid init response \"%s\" %d.)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task's state invalid."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-7-RATERR103

SEVERITY: Information
FORMAT: "RAT \"%s\", task \"%s\" (%d) changes from \"%s\" (%d) to \"%s\" (%d).)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The regression test (callback) child task received and processed a state change request."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR104

SEVERITY: Warning
FORMAT: "RAT \"%s\" priority (%d) is too low, task aborted."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT task was spawned at a priority such that no child tasks could be spawned at a lower priority. Reassign a more reasonable value to the RAT in the ctc_app_table.h file."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR105

SEVERITY: Warning
FORMAT: "RAT \"%s\" priority (%d) is low, this may affect switchover timing!"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT task was spawned at a priority such that the interactions between itself and its children may be delayed. This could result in long delays during switchover processing. It is recommended that the RAT be run at very high priorities (values less than twenty)."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR106

SEVERITY: Warning
FORMAT: "\"%s\" RAT task context user event handler failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT task context event handler function returned a value other than OK to the RAT task. This should never happen and is indicative a of serious failure within the application event function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR107

SEVERITY: Warning
FORMAT: "\"%s\" RAT task context user initialization failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT task context initialization function returned a value other than OK to the RAT task. This should never happen and is indicative a of serious failure within the application event function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR108

SEVERITY: Warning
FORMAT: "\"%s\" RAT task context user role change function failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The RAT task context role change function returned a value other than OK to the RAT task. This should never happen and is indicative a of serious failure within the application function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR109

SEVERITY: Warning
FORMAT: "Invalid event list detected for \"%s\" RAT, task \"%s\" (%d)."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The user supplied RAT event registration data for the child entry event lists are bad."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-5-RATERR110

SEVERITY: Warning
FORMAT: "Invalid event list detected for \"%s\" RAT context task."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The user supplied RAT event registration data for the root task context event lists are bad."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info
RAT-5-RATERR111
SEVERITY: Warning
FORMAT: "\"%s\" RAT, task \"%s\" (%d) timed out during initialization."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The task exceeded the amount of time alotted to call the ratChildInitalizedAck() function."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

RAT-4-RATERR112

SEVERITY: Error
FORMAT: "RAT ssiFree() failed for addr 0x%08X length %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The memory free failed."
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. Do the same with 'dsplog' command. If you cannot determine the nature of the error from the error message text or from the 'dsperr'/'dsplog' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

DDTS "config-upload"

CUTS-7-CUTS_UPDT_DONE

SEVERITY: Information
FORMAT: "EVNT: CUT:API to update %s for filetype %d done"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Update to FCB and mibs for filetype specified done"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-SEND_CUTV_FAIL

SEVERITY: Information
FORMAT: "EVNT: CUT:Failed to send %s message for filetype %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "API to send message to the CUTV task failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-UPD_FCB_FAIL

SEVERITY: Information
FORMAT: "Line:%d:Failed to update FCB"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "API to update the FCB returned ERROR"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-TMR_REINIT_FAIL

SEVERITY: Information
FORMAT: "Line:%d:Failed to reinit timer with reason %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to reinitiate timers"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-SEMGIVE_FAIL

SEVERITY: Information
FORMAT: "line:%d:could not give up sem %s: errno 0x%x"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "semgive for sem failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_FILE_MUTEX

SEVERITY: Information
FORMAT: "EVNT: CUT:(cuts) FileIndex %d cannot be be createdsince another CONN/STATIC-CONN file is being created "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Config upload should not create both conn and conn-update files together. If there is another conn/conn-update file running, the request will be rejected"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-5-TXID_GET_FAILED

SEVERITY: Warning
FORMAT: "%d: Config upload failed to receive a valid TxId from the card, errno = 0x%x"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Config upload failed to receive a valid TxId from the card"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-INV_TXID

SEVERITY: Information
FORMAT: "%d: fileType = %d, card TxID= %d less than req TxID = %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The requested TxID is greater than the card TxID"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CANNOT_PROCEED

SEVERITY: Information
FORMAT: "%d: fileType = %d, reqType= %d,reqTxID= %d: cutwCanCreationProceed returned FALSE"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Either due to mutual exclusion or the reqTxID being greater than the card TxID, cfgupload cannot continue"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_UPDT_FAIL

SEVERITY: Information
FORMAT: "EVNT: CUT:API to update %s returned error for filetype %d "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Update to FCB and mibs for filetype specified failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-RMTCLOSE_FAIL

SEVERITY: Information
FORMAT: "On line %d: ssiRmt close failes errno= 0x%x"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "ssiremoteclose API returned error"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-INVALID_PARAM

SEVERITY: Warning
FORMAT: "%d: Invalid parameter passed"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Invalid parameter was received by the function"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-TXID_GET_FAILED

SEVERITY: Warning
FORMAT: "%d: Config upload failed to receive a valid TxId from the card"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Config upload failed to receive a valid TxId from the card"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-TIME_GET_FAILED

SEVERITY: Warning
FORMAT: "%d: Failed to get current time of day"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to get current time of day"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-OPEN_FAILED

SEVERITY: Warning
FORMAT: "%d: Failed to open file %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to open a file"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-FILE_NAME_PARSE

SEVERITY: Warning
FORMAT: "%d: Failed to parse filename %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to parse a filename"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-BITMAP_FAILURE

SEVERITY: Warning
FORMAT: "%d: Failed to get connection bitmap"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to get the connection bitmap"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-ALARM_FILE_PATH

SEVERITY: Warning
FORMAT: "%d: Failed to get alarm file path"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to get alarm file path"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-INVALID_ALARM_F

SEVERITY: Warning
FORMAT: "%d: Failed to get connection bitmap"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to get the connection bitmap"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-ALARM_READ_FAIL

SEVERITY: Warning
FORMAT: "%d: Failed to read enough data from alarm file"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to read enoughd data from alarm file"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-NULL_ERRHDLR

SEVERITY: Warning
FORMAT: "%d: No error handler found, fileType=%d, i=%d, j=%d, k=%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to read enoughd data from alarm file"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-FILE_READFAIL

SEVERITY: Warning
FORMAT: "WARN: CUT:(cutv) cannot open file (fd:%d, name:%s) with
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutv failed open file with read permission"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-REMOVE_FAIL

SEVERITY: Warning
FORMAT: "WARN: CUT:(cutv) remove failed for %s in
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutv cannot remove the file. remove failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-VLDN_CNTR_EXCEE

SEVERITY: Information
FORMAT: "EVNT: CUT:(cutv) failed to open file with
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "validation counter exceeded threshold"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-RMT_FILE_IOCTL_

SEVERITY: Warning
FORMAT: "WARN: CUT:(cutv) remote file ioctl fail in %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "remote file ioctl failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-LATEST_STATIC_F

SEVERITY: Warning
FORMAT: "%d: Failed to find the latest static conn file"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to find the latest static conn file"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-ENGINE_INVALID_

SEVERITY: Warning
FORMAT: "%d: Invalid request given to the engine: %d, filetype =%d\n"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Invalid request given to the engine"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-ENGINE_REQ_PROC

SEVERITY: Warning
FORMAT: "%d: Invalid request processing entry in the request matrix, reqtype=%d, filetype =%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Invalid request processing entry in the request matrix"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-ENGINE_INVALID_

SEVERITY: Warning
FORMAT: "%d: Invalid processing parts reqtype=%d, filetype =%d, totalProcessingParts=%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Invalid request processing entry in the request matrix"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-INVALID_SLOT

SEVERITY: Warning
FORMAT: "%d: Invalid slot "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to get slot# from CTC"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-ENGINE_INVALID_

SEVERITY: Warning
FORMAT: "%d: Invalid slot "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to get slot# from CTC"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-ENGINE_SEEK_LEN

SEVERITY: Warning
FORMAT: "%d: Failed to seek into file for updating length"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to seek into file for updating length"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-REPLICATE_FAIL

SEVERITY: Warning
FORMAT: "%d: Failed to replicate the file %s to standby PXM"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Asynchronous file replication API failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-INVALID_REQUEST

SEVERITY: Warning
FORMAT: "%d: Config upload received a requested TxId larger than the card TxId"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Config upload received a request to create incremental file with TxId larger than the one on the card"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-TXID_AUDIT_FAIL

SEVERITY: Warning
FORMAT: "%d: Config upload requested audit of card TxId and the audit failed"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Config upload received a request to create incremental file with TxId larger than the one on the card. It requested audit of card TxId and it could not be fixed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-CHKSUM_FAILURE

SEVERITY: Warning
FORMAT: "%d: Checksum failed for file %s: compChecksum=0x%x, readChecksum=0x%x"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "One byte checksum in the file did not match with the calculated checksm"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-MEM_ALLOC_FAIL

SEVERITY: Warning
FORMAT: "%d: Failed to allocate %d bytes in memory"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Memory allocation failure"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-ALARM_FILE_BUFF

SEVERITY: Warning
FORMAT: "%d: Failed to get latest alarm file data "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to get latest alarm file data from cPro/conPro applications"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-STBY_REMOVE_FAI

SEVERITY: Warning
FORMAT: "%d: Failed to remove %s from stdby"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Failed to get latest alarm file data from cPro/conPro applications"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTR-5-CUT_RAM_FILE

SEVERITY: Warning
FORMAT: "EVNT CUT(cutram) Ftp Request for File%s Physical Slot Number Failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Unable to determine the Physical Slot Number for the file."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTR-5-CUT_RAM_NAME

SEVERITY: Warning
FORMAT: "EVNT CUT(cutram) Ftp Request for File%s Ram disk name Failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Unable to determine the Ram disk name for the file."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTR-5-CUT_RAM_LOG

SEVERITY: Warning
FORMAT: "EVNT CUT(cutram) Ftp Request for File%s Logical Slot%d Phy Slot Conv Failed."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Unable to convert the Logical Slot to a Physical Slot Number."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "config-upload"

CUTS-7-CUTS_DIR_FOUND

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

CUTS-4-CUTS_NON_DIR_FI

SEVERITY: Error
FORMAT: "ERR CUT(cuts) found a non directory entry of name %s found."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "CUTS found a non directory entry of name CUT. Please remove this file and create a directory C:/CUT instead. Otherwise, Config Upload will fail."
RECOMMENDED ACTION: Make sure the C:/CUT is a directory and not a file name. If it is a file name, remove the file and create C:/CUT directory. If the card is active, try to copy a file into that C:/CUT directory. If the operation is not sucessfull, contact TAC.
REQUIRED INFO: If CLI available, capture the following command output before contact TAC
1) dir "C"
2) dspversion
3) dspdate
4) dsplog -mod CUTS

CUTS-4-CUTS_IOCTL_FAIL

SEVERITY: Error
FORMAT: "ERR CUT(cuts) Can not get stats for %s "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Scheduler task is not able to determine whether C:/CUT is a directory or a file. Config Upload will fail if C:/CUT directory does not exist. "
RECOMMENDED ACTION: Make sure the C:/CUT is a directory and not a file name. If it is a file name, remove the file and create C:/CUT directory. If the card is active, try to copy a file into that C:/CUT directory. If the operation is not sucessfull, contact TAC.
REQUIRED INFO: If CLI available, capture the following command output before contact TAC
1) dir "C"
2) dspversion
3) dspdate
4) dsplog -mod CUTS

CUTS-4-CUTS_OPEN_FAILE

SEVERITY: Error
FORMAT: "ERR CUT(cuts) unable to open dir/file %s "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Scheduler task is not able to open C drive. This cause C:/CUT directory not being able to create. Config Upload will fail."
RECOMMENDED ACTION: Make sure the C:/CUT is a directory and not a file name. If it is a file name, remove the file and create C:/CUT directory. If the card is active, try to copy a file into that C:/CUT directory. If the operation is not sucessfull, contact TAC.
REQUIRED INFO: If CLI available, capture the following command output before contact TAC
1) dir "C"
2) dspversion
3) dspdate
4) dsplog -mod CUTS

CUTS-5-CUTS_MKDIR_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cuts) unable to create directory %s "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Scheduler Task is unable to create a directory. Config Upload will fail if C:/CUT directory does not exist. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-ACK_TIMEOUT

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) ACK timeout, task status=\"%s\", index=%d, file type=%d, threshold=%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Scheduler task timeout while waiting acknowlegdemeent from worker task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-4-CUTS_EPID

SEVERITY: Error
FORMAT: "ERR CUT(cuts) Creation of CUTS EPID \"%s\" failed rc = 0x%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed to create epid for cuts. This might result in Config Upload not able to function correctly."
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTS-5-CUTS_TIMER_CREA

SEVERITY: Warning
FORMAT: "ERR CUT(cuts) Creation of timer failed rc= 0x%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Timer Creation failed. This might result in Config Upload not able to function correctly."
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTS-4-CUTS_ATTHDLR

SEVERITY: Error
FORMAT: "ERR CUT(cuts) Attaching of handler \"%s\" failed Epid = 0x%08X rc= 0x%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Attaching of handler to a cuts epid has failed. The epid name, number and error code are listed. This might result in Config Upload not able to function correctly"
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTS-5-CUTS_TMR_SCHD

SEVERITY: Warning
FORMAT: "WARN CUT(cuts) failed to schedule timer in \"%s\" timeout value = %d, timer type = %d, rc= 0x0%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "failed to schedule timeout. This might cause a request for Config Upload to be drop."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-5-CUTS_TMR_CNCL

SEVERITY: Warning
FORMAT: "WARN CUT(cuts) failed to cancel timer in \"%s\" timer type = %d, rc= 0x0%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "failed to cancel timer"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-4-CUTS_IPC_FREE_E

SEVERITY: Error
FORMAT: "ERR CUT(cuts) IPC Message Free Failed rc = 0x%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error in Freeing IPC message. Potential memory leak."
RECOMMENDED ACTION: If this event shows up exessively(about 5 or more times) in the event log, please log a bug and contact TAC immediatly. This is a potentential memory leak.
REQUIRED INFO: If CLI available, capture the following command output before contacting TAC
1) dspversion
2) dspdate
3) dspmempart 2 1
4) dsplog -mod CUTS
5) dsplog -mod CUTWRKR

CUTS-5-IPCFAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cuts) IPC SEND FAILED TO \"%s\" from \"%s\" request%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "IPC send failed. This will result in Config Upload file creation request being dropped."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-5-IPC_ALLC_FAILED

SEVERITY: Warning
FORMAT: "WARN CUT(cuts) failed to allocate ipc buffer in \"%s\"."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "failed to allocate ipc buffer. This will result in Config Upload file creation request being dropped."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_INVALID_RQ

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) Invalid request received by cuts from system epid req = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid request received by Scheduler task(CUTS)"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_INVALID_RQ

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) Request received by cuts while in invalid state, rq ignored state = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Request sent to cuts while cuts in invalid state"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-5-CUTS_WRKR_UPDAT

SEVERITY: Warning
FORMAT: "WARN CUT(cuts) failed to update the worker task of index (%d) to state %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "CUTS unable to update worker task state. This might cause the death of the worker task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-TMR_ERROR

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) failed to find a worker for expired timerID = %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "CUTS timer expired with no associated worker task found"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-5-RNWY_TASK

SEVERITY: Warning
FORMAT: "WARN CUT(cuts)found a worker task(%d)\"%s\" RUNNING yet not working on any file"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "CUTS timer expired, found a task in running with no work"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-5-BAD_RSPNSE

SEVERITY: Warning
FORMAT: "WARN CUT(cuts) invalid epid in an epid response or child active message from 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "CUTS received a bad epid_response or child active msg"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_FC_FAILED

SEVERITY: Information
FORMAT: "EVNT: CUT:(cuts) failed to process file creation request: %s for file 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts failed to service file creation request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-4-BAD_FILEINDX

SEVERITY: Error
FORMAT: "ERR CUT(cuts) Invalid File index found in \"%s\" file Index = %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts found an invalid file index. This might cause Config Upload file creation to fail. "
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTS-7-FILE_STATE_GENE

SEVERITY: Information
FORMAT: "EVNT CUT(cuts)request made to generate an already generating file ignoredfileIndex = %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts got a request to generate a file already being generated"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_CHILD_ACTI

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) rcvd a child active message from taskid %d, taskname%s."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts got a child active message from a task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_EPID_RESPO

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) %s task is registered with Scheduler task as taskid %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts got an EPID response message from a task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_FC_DONE

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) rcvd file creation done from taskid %d, file%d "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts got a file creation done from task"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-5-CUTS_TRAP_NOTAS

SEVERITY: Warning
FORMAT: "WARN CUT(cuts) sent TRAP cwBulkNoTaskAvailable(60904) for file%d "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts sent trap to CWM 60904"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_TRAP_START

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) sent TRAP cwBulkFileCreationStarted(60901) for file%d "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts sent trap to CWM 60901"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_TRAP_FAIL

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) sent TRAP cwBulkFileCreationFailed(60905) for file%d "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts sent trap to CWM 60905 which signals file creation failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_TRAP_DONE

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) sent TRAP cwBulkFileCreationDone(60902) for file%d "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts sent trap to CWM 60902"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_TRAP_ABRT

SEVERITY: Information
FORMAT: "EVNT CUT(cuts) sent TRAP cwBulkFileCreationAborted(60903) for file%d "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cuts sent trap to CWM 60903"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-TRAP_SEND_FAIL

SEVERITY: Information
FORMAT: "line%dTrap not sent by %s for file%d "
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "API to send trap failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTS-7-CUTS_UPDT_FAIL

SEVERITY: Information
FORMAT: "EVNT CUTAPI to update %s returned error for filetype %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Update to FCB and mibs for filetype specified failed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "config-upload"

CUTW-4-CUTW_EPID

SEVERITY: Error
FORMAT: "ERR CUTCreation of CUTW EPID \"%s\" failed rc = 0x%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Failed to create epid(end point communication) for cutw."
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTW-4-CUTW_TIMER_CREA

SEVERITY: Error
FORMAT: "ERR CUT Creation of timer failed rc= 0x%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Timer Creation 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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTW-4-CUTW_ATTHDLR

SEVERITY: Error
FORMAT: "ERR CUTAttaching of handler \"%s\" failed Epid = 0x%08X rc= 0x%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Attaching of handler to a cutw epid has failed. The epid name, number and error code are listed."
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTW-5-CUTW_TMR_SCHD

SEVERITY: Warning
FORMAT: "ERR CUT failed to schedule timer in \"%s\" timeout value = %d, timer type = %d, rc= 0x0%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "failed to schedule timeout"
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTW-5-CUTW_TMR_CNCL

SEVERITY: Warning
FORMAT: "ERR CUTfailed to cancel timer in \"%s\" timer type = %d, rc= 0x0%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "failed to canecl timer"
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTW-4-CUTW_IPC_FREE_E

SEVERITY: Error
FORMAT: "ERR CUT IPC Message Free Failed rc = 0x%08X."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Error in Freeing IPC message"
RECOMMENDED ACTION: If this event shows up exessively(about 5 or more times) in the event log, please log a bug and contact TAC immediatly. This is a potentential memory leak.
REQUIRED INFO: If CLI available, capture the following command output before contacting TAC
1) dspversion
2) dspdate
3) dspmempart 2 1
4) dsplog -mod CUTS
5) dsplog -mod CUTWRKR

CUTW-5-IPCFAIL

SEVERITY: Warning
FORMAT: "ERR CUT IPC SEND FAILED TO \"%s\" from \"%s\" request%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "IPC send 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: If CLI available, capture the following command output before contacting TAC
1) dspversion
2) dspdate
3) dspmempart 2 1
4) dsplog -mod CUTS
5) dsplog -mod CUTWRKR

CUTW-4-IPC_ALLC_FAILED

SEVERITY: Error
FORMAT: "ERR CUT failed to allocate ipc buffer in \"%s\"."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "failed to allocate ipc buffer. This will cause CUTS not able to communicate with this 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: If CLI available, capture the following command output before contacting TAC
1) dspversion
2) dspdate
3) dspmempart 2 1
4) dsplog -mod CUTS
5) dsplog -mod CUTWRKR

CUTW-5-CUTW_INVALID_RQ

SEVERITY: Warning
FORMAT: "ERR CUT Invalid request received by cutw from system epid req = %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Invalid request received"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-4-CUTW_EPID_RESOL

SEVERITY: Error
FORMAT: "ERR CUT CUTW %s could NOT resolve CUTS epid"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Not able to resolve the scheduler task's epid"
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTW-5-CUTW_WRKR_UPDAT

SEVERITY: Warning
FORMAT: "ERR CUT failed to update the worker task of index (%d) to state %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "CUTW unable to update worker task state"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-4-CUTW_INIT_PTR

SEVERITY: Error
FORMAT: "ERR CUT CUTW Task init failed due to a NULL taskControlBlockPtr in %s, tid = 0x%0X"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "CUTW init failed due to a null task controlblock ptr"
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: If CLI available, please capture the following command output before contact TAC
1) dspversion
2) dspdate
3) dsplog -mod CUTS
4) dsplog -mod CUTWRKR
5) dsplog

CUTW-5-CUTW_FC_FAILED

SEVERITY: Warning
FORMAT: "ERR CUT cutw failed to process file creation request for file 0x%08X."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to validate file creation request"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-BAD_FILEINDX

SEVERITY: Warning
FORMAT: "ERR CUT Invalid File index found in \"%s\" file Index = %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw found an invalid file index "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-CUTWFILENAME

SEVERITY: Information
FORMAT: "EVNT CUTfilename created for the request is \"%s\" file Index = %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw created the name for the file creation request "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-W_RATEVENTPENDI

SEVERITY: Information
FORMAT: "EVNT CUT RAT event %d pending found while creating file Index = %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw had to abort while creating a file due to rat events "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-NULL_FILEP

SEVERITY: Information
FORMAT: "EVNT CUT(cutw) NULL FILEPTR PASSED IN to \"%s\" routine"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw found an invalid file ptr "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-TASK_STATUS_TRA

SEVERITY: Information
FORMAT: "EVNT CUT(cutw) Task status transition from \"%s\" to \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "Task is transitioning from one state to another"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-SEMTAKE_FAIL

SEVERITY: Information
FORMAT: "EVNT CUT(cutw) Can't take semaphore for \"%s\" in function \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw was not abe to take a semaphore"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-SEMGIVE_FAIL

SEVERITY: Information
FORMAT: "EVNT CUT(cutw) Can't release semaphore for \"%s\" in function \"%s\"."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw was not abe to release a semaphore"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-NULL_PTR

SEVERITY: Information
FORMAT: "EVNT CUT(cutw) NULL pointer PASSED IN to \"%s\" routine"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw found a null ptr "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-MEM_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)failed to allocate mem for %s for file index %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to allocate buffer. This Config Upload file creation request will not be successfull. "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-MEMDEALL_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)failed to deallocate mem for %s for file index %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to deallocate buffer. This could lead to memory leak "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-RTOID_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)failed to write ROOT OID for file index %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to write root oid which cause this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-TBLOID_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)failed to write ROOT OID for file index %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to write table oid which cause this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-CNFOID_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)failed to write item OID %d,col %d, for file index %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to write item oid which cause this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-CNFVRBND_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)failed to write CNFVRBND table %d,col %d, for file index %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to write cnfg varbind which causes this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-FINDOBJ_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)find_object failed for oidTbl->oidListInx=%u for file %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw can not not find the current OID which causes this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-GTNXT_FAIL

SEVERITY: Information
FORMAT: "EVNT CUT(cutw)Empty Table found, continuing.. for file %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw found an empty table "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-WRITE_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)failed to write %s for file %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to write data to file which causes this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-GET_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw) Get failed for object with serial number%d for file %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to do a get operation which causes this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-GETNEXT_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw) Get-Next failed for object with serial number %d with errno %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to do a get-next operation which causes this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-GETSCLR_FAIL

SEVERITY: Warning
FORMAT: "ERR CUT(cutw) Get failed for object table %d,col %d for file %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw write failed "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-IOCTL_FAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw)call to %s failed while creating file %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw ioctl call failed "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-7-CR_RESULT

SEVERITY: Information
FORMAT: "EVNT CUT(cutw)FILE CREATION RESULTED IN %s for file %d File size %ld Checksum %x"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw file creation result "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-FILE_ERR

SEVERITY: Warning
FORMAT: "ERR CUT(cutw) %s for file %d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw file creation result "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-5-WRITE_BYTESFAIL

SEVERITY: Warning
FORMAT: "WARN CUT(cutw) Write Fail for File %d requested bytes %d bytes written %d."
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw failed to write requested number of data to file which causes this Config Upload file creation aborted "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CUTW-4-MAX_ROWS_EXCEED

SEVERITY: Error
FORMAT: "WARN CUT(cutw) Write Fail for File %d Too many rows limit is %d, currently %d. oidTblInx=%d"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "cutw aborted the file creation because number of rows allowed for this file exceeded the defined limit"
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: "An error is detected by hardware device drivers. Possible causes are NOVRAM access problem, driver configuration not supported by current hardware, or invalid parameters being passed to the drivers. When hardware fails to be initialized, card will not come up."
RECOMMENDED ACTION: "Please capture following information and 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 AXSM
1. dspcd
2. dspver
3. dsplns "

DDTS "diskdb"

DB2S-4-DBSVR_RESV_NO_D

SEVERITY: Error
FORMAT: "Slot %d: Slot reserved but No DB present"
FLAG: Write Bram
THROTTLING: One Tick
EXPLANATION: " The slot is reserved from the SHM perspective but its DB2 directory does not have any DBs for the slot"
RECOMMENDED ACTION: "Call TAC"
REQUIRED INFO: "Save event logs, error logs and ll from D:/DB2"

DB2S-5-PSEURESV_NO_DB

SEVERITY: Warning
FORMAT: "Slot %d: Slot is psuedo resv but No DB present. %s"
FLAG: Write Bram
THROTTLING: One Tick
EXPLANATION: " The slot is pseduo reserved from the SHM perspective but its DB2 directory does not have any DBs for the slot"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-4-DBCLNT_COMEP

SEVERITY: Error
FORMAT: "Error 0x%x on %s DB Client Communication Port"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module has failed to create a message queue. This could be due to internal error or memory corruption or hardware problem. This error results in failing the initialization of the DB Manager Client module. As a result, the card on which this error occured will not come up."
RECOMMENDED ACTION: "Try rebooting the card. If this error persists either the image from the flash/disk could be bad or the card could be faulty. In this case, try changing the card."
REQUIRED INFO: "Collect the event and error logs."

DB2C-3-DBCLNT_EPHNDLR

SEVERITY: Minor Alert
FORMAT: "Error 0x%x in attaching the msg handler to DBCLNT epid %x"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module has failed to attach message handler to the message queue. This could be due to internal error or memory corruption or hardware problem. This error results in failing the initialization of the DB Manager Client module. As a result, the card on which this error occured will not come up."
RECOMMENDED ACTION: "Try rebooting the card. If this error persists either the image from the flash/disk could be bad or the card could be faulty. In this case, try changing the card."
REQUIRED INFO: "Collect the event and error logs."

DB2C-4-DBCLNT_TMRERR

SEVERITY: Error
FORMAT: "Error 0x%x in creating the ssi sync timer for DBCLNT"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module has failed to create a timer . This could be due to internal error or memory corruption or hardware problem. This error results in failing the initialization of the DB Manager Client module. As a result, the card on which this error occured will not come up."
RECOMMENDED ACTION: "Try rebooting the card. If this error persists either the image from the flash/disk could be bad or the card could be faulty. In this case, try changing the card."
REQUIRED INFO: "Collect the event and error logs."

DB2C-4-DBCLNT_RETXQ

SEVERITY: Error
FORMAT: "Error 0x%x creating DB Client retransmission queue"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module has failed to create a retransmission queue This could be due to internal error or memory corruption or hardware problem. This error results in failing the initialization of the DB Manager Client module. As a result, the card on which this error occured will not come up."
RECOMMENDED ACTION: "Try rebooting the card. If this error persists either the image from the flash/disk could be bad or the card could be faulty. In this case, try changing the card."
REQUIRED INFO: "Collect the event and error logs."

DB2C-5-DBCLNT_CTCAPI

SEVERITY: Warning
FORMAT: "Error %x on call to %s"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client failed when called the specified API."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-7-DBCLNT_STERR

SEVERITY: Information
FORMAT: "%s unavailable due to invalid state <%x>. Info<%s>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Critical external resource indicated is unavailable this may results in subsequent requests failure"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_UNEXPEVT

SEVERITY: Warning
FORMAT: "Unexpected %s 0x%x. %s %d, %s %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Client module Received CTC events that belongs to other logical slot which the client did not registered for."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-3-DBCLNT_VER_NOTS

SEVERITY: Minor Alert
FORMAT: "Message version 0x%x not supported. Current version is %x"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module received an interface message of which the version is incompatible with the version that the DB Client module is running. This could be due to the DB Manager Server module and the DB Manager Client module running different versions that are not compatible or due to memory corruption. This may result in either failure of the initialization of the DB Manager Client module or a provisioning request."
RECOMMENDED ACTION: "Try resetting the card. If the error persists, try changing the card to rule out the hardware issue. If the error still persists, call TAC."
REQUIRED INFO: "Collect the event and error logs."

DB2C-4-DBCLNT_INVEVTGR

SEVERITY: Error
FORMAT: "Invalid DB Client event group <%d>, arg = 0x%x"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module recieved a message that doesn't belong to any of the known and supported event groups. This could be due to the DB Manager Server module and the Client module running different versions that are not compatible or due to memory corruption. This may result in either failure of the initialization of the Client module or a provisioning request."
RECOMMENDED ACTION: "Try resetting the card. If the error persists, try changing the card to rule out the hardware issue. If the error still persists, call TAC."
REQUIRED INFO: "Collect the event and error logs."

DB2C-5-DBCLNT_INVACCES

SEVERITY: Warning
FORMAT: "%s AppId <0x%x> invalid Access on %s %d. Current %s %s. Expected %s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Client task encountered an invalid access situation as indicated"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-4-DBCLNT_INVMSG

SEVERITY: Error
FORMAT: "%s received invalid message <%s>, event grp = %s, ApplName=%s. Info<%s>"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module recieved an unknown or unsupported message. This could be due to the DB Manager Server module and the Client module running different versions that are not compatible or due to memory corruption. This may result in either failure of the initialization of the Client module or a provisioning request."
RECOMMENDED ACTION: "Try resetting the card. If the error persists, try changing the card to rule out the hardware issue. If the error still persists, call TAC."
REQUIRED INFO: "Collect the event and error logs."

DB2C-5-DBCLNT_UNAVL

SEVERITY: Warning
FORMAT: "<%s> Request failed. %s State<%s>"
FLAG: Stack Trace | Write to Bram
THROTTLING: One Tick
EXPLANATION: "DB Client task rejected the request stated due to Resource specified unavailable."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-4-DBCLNT_RECVMSG

SEVERITY: Error
FORMAT: "Error 0x%x receiving IPC message on DB Client Port"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module received a NULL message. This could be due to memory corruption or hardware problem. This may result in failing the card to come up or the provisioning request."
RECOMMENDED ACTION: "Try resetting the card. If the error persists, try changing the card to rule out the hardware issue. If the error still persists, call TAC."
REQUIRED INFO: "Collect the event and error logs."

DB2C-5-DBCLNT_RETXFAIL

SEVERITY: Warning
FORMAT: "Error 0x%x on putting <%s> REQ in ReTxQ to %s DB Server"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Client task failed to put the message on ReTxQ"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_SENDFAIL

SEVERITY: Warning
FORMAT: "Error 0x%x on sending message <%s> to %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Client task failed to send message to DB Server"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_REPLYFAI

SEVERITY: Warning
FORMAT: "Error 0x%x replying to applId <0x%x> on event%s, msg type%s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Client task failed to send reply to the Appl"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_MSGALLOC

SEVERITY: Warning
FORMAT: "Error 0x%x allocating IPC message buffer of size 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Client task failed to send reply to the Appl"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-6-DBCLNT_TXCLEANU

SEVERITY: Notice
FORMAT: "TxId <0x%x> for <%s> Server not cleaned up on <%s>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Transaction was not cleaned up properly on the resource specified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_RESPTMOU

SEVERITY: Warning
FORMAT: "Response Timeout for TxId <%d> to Svr <%s>. TxState%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Client task failed to receive response for a transaction after three message retransmission attempts to the specified db server. Current transaction state is also specified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_MAXEXCEE

SEVERITY: Warning
FORMAT: "Max %s per Logical slot reached. Created=%d, Max Allowed=%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Client task failed to process the DB or TBL Create Request message due to max per logical slot reached."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_NOFREEID

SEVERITY: Warning
FORMAT: "Can't find unassigned %s Id. Num of %s Created = %d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Client task failed to assign a dbId or tblId. This indicates cleanup problem in cntrl blk table"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DB2CLNT_INVAPPI

SEVERITY: Warning
FORMAT: "Application Id received = 0x%x exceed max value of 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Client task failed convert the application Id received from the API request message to internal value for array indexing"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_INVTXID

SEVERITY: Warning
FORMAT: "Invalid TxId <%d> for %s msgType=%s from DB Svr=%s. Svr Sts=%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Client task recieved an unknown transaction Id from the specified DB Server for the event group and msg type indicated."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_TXMSG

SEVERITY: Warning
FORMAT: "%s MsgType=%s received for TxId=%d different from REQ MsgType=%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Msg Type received for the Event Group indicated is different from the message type of the API Request."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_OUTOFRAN

SEVERITY: Warning
FORMAT: "%s value <0x%x> out of range. Max allowed 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The specified value is out of the allowed range"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_NOTOWNER

SEVERITY: Warning
FORMAT: "Appl Id <0x%x> not owner of Db Id <0x%x> which is owned by <0x%x>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Not owner application is trying to access the db"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_IDNONEXI

SEVERITY: Warning
FORMAT: "%s %s <0x%x> received from Appl_Id <0x%x> does not exists"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The specified data value does not exists. This indicates either the object has never been created or it has been deleted."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-4-DBCLNT_INFOERR

SEVERITY: Error
FORMAT: "%s control info for %s <0x%x> corrupted %s in %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module's internal control info blk of the indicated object has been corrupted. This could be due to memory corruption or internal error. This may result in card not coming up or failure of provisioning."
RECOMMENDED ACTION: "Reset the card."
REQUIRED INFO: "Take a hot-dump if it is on controller card. If this error occured on a Service Module, call TAC to take a core dump of the Service Module. Collect event logs and error logs."

DB2C-6-DBCLNT_UNREG

SEVERITY: Notice
FORMAT: "DBCLNT All DBs unregistered for Lslot = %d, SwId = 0x%x by %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Client successfully unregistered all DBs and cleaned up its control structures for specified logical slot and sw Id."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_NONREDUP

SEVERITY: Warning
FORMAT: "Update Failed on STBY DB Server for TBL Id <0x%x>. Svr State = %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Update operation to the table specified failed on the standby DB Server with the indicated Svr State Problem have been reported to CTC to check card's status"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_INTERNAL

SEVERITY: Warning
FORMAT: "%s DB Client Internal Error <%s> in %s"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "Internal error detected on the specified DB Client"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_INVSVRRE

SEVERITY: Warning
FORMAT: "%s %s0x%x expects0x%x or 0x%x."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Response received from the Server has invalid value for the specified one field."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-4-DBCLNT_INVSVRRE

SEVERITY: Error
FORMAT: "%s %s0x%x, expects0x%x, %s0x%x, expects0x%x."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module has received a response with invalid values from the Server module. This could be due to memory corruption either on the controller card or on the Client card. This may result in card not coming up or failure to provision."
RECOMMENDED ACTION: "Try resetting the Client card. If the problem still persists, try changing the card. If the problem still perists, call TAC."
REQUIRED INFO: "If the problem occured on the controller card, take a hot dump. If the problem occured on a service module, take the hot dump of the controller card and call TAC to collect the core dump for the Service Module. Collect event and error logs."

DB2C-4-DBCLNT_INVSVRRE

SEVERITY: Error
FORMAT: "%s %s0x%x expects 0x%x or 0x%x, %s0x%x, expects0x%x."
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module has received a response with invalid values from the Server module. This could be due to memory corruption either on the controller card or on the Client card. This may result in card not coming up or failure to provision."
RECOMMENDED ACTION: "Try resetting the Client card. If the problem still persists, try changing the card. If the problem still perists, call TAC."
REQUIRED INFO: "If the problem occured on the controller card, take a hot dump. If the problem occured on a service module, take the hot dump of the controller card and call TAC to collect the core dump for the Service Module. Collect event and error logs."

DB2C-4-DBCLNT_INVPEERR

SEVERITY: Error
FORMAT: "Invalid %s Request from %s for %s 0x%x. %s0x%x, expects0x%x in %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client on the Active card received a request with invalid parameters from its peer on the Standby card. This could be due to memory corruption on either the Active card or on the Standby card. If this error occured, the Standby card fails to come up."
RECOMMENDED ACTION: "Try resetting the Standby card. If the problem persists, call TAC."
REQUIRED INFO: "Collect event and error logs. If the error occured on the controller card, take the hot dump of the Active controller card. If this error occured on a service module, call TAC to take the core dump of the Active service module."

DB2C-4-DBCLNT_INVPEERR

SEVERITY: Error
FORMAT: "Invalid %s Request from %s for %s 0x%x. %s0x%x, expects0x%x. %s0x%x, expects0x%x in %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client on the Active card received a request with invalid parameters from its peer on the Standby card. This could be due to memory corruption on either the Active card or on the Standby card. If this error occured, the Standby card fails to come up."
RECOMMENDED ACTION: "Try resetting the Standby card. If the problem persists, call TAC."
REQUIRED INFO: "Collect event and error logs. If the error occured on the controller card, take the hot dump of the Active controller card. If this error occured on a service module, call TAC to take the core dump of the Active service module."

DB2C-5-DBCLNT_DUPREQ

SEVERITY: Warning
FORMAT: "%s %s %s %s %s 0x%x %s 0x%x %s %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The request has already been received and processed"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-DBCLNT_BAD_SWID

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

DB2C-4-DBCLNT_SPAWN_ER

SEVERITY: Error
FORMAT: "%s failed to spawn task - errno %x"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module has failed to spawn one of its children. This could be due to internal error or memory corruption. If this error occures, the card doesn't come up."
RECOMMENDED ACTION: "Try resetting the card or replacing the card. If the error still persists, call TAC."
REQUIRED INFO: "Collect event and error logs."

DB2C-4-DBCLNT_MEM_ERR

SEVERITY: Error
FORMAT: "%s failed memory alloc(free) - errno %x"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module failed to allocate memory. This could be due to either shortage of memory or leakage of memory. The problem card will fail to come up."
RECOMMENDED ACTION: "Call TAC."
REQUIRED INFO: "Collect event and error logs."

DB2C-4-DBCLNT_CONV_OP_

SEVERITY: Error
FORMAT: "%s Op<%s> Obj<%s> Id<%x> Errno<0x%x> ExtraInfo<%x>"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module has failed for the specified reason while upgrading the databases. This could be due to memory corruption or internal error. This results in card not coming up."
RECOMMENDED ACTION: "Try resetting the card or changing the card. If the error still persists, call TAC."
REQUIRED INFO: "Collect event and error logs."

DB2C-5-UPGFAIL

SEVERITY: Warning
FORMAT: "0x%x Db Upgrades from %d.%d.%d.%d to %d.%d.%d.%d FAILED"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The Db upgrade from the specified version to the specified version has failed."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-1-TASKSPAWN

SEVERITY: Fatal
FORMAT: "Failed to spawn the upgrade task %s, errno = 0x%x"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Client module failed to spawn the specified child task which performs the Db upgrades. This error could occur due to memory corruption or internal error. If this error occurs, the card doesn't come up."
RECOMMENDED ACTION: "Try resetting the card or changing the card. If the error still persists, call TAC."
REQUIRED INFO: "Collect event and error logs."

DB2C-5-TBLINFCOR

SEVERITY: Warning
FORMAT: "%s Lslot=%d TblName=%s MaxRec=%d ExpMaxRec=%d RecSize=%d ExpRecSize=%d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Client received the table information recovery response for a table different from what it requested."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-RECNACK

SEVERITY: Warning
FORMAT: "Recd NACK for Table Info Recover REQ Lslot=%d TblName=%s Reason=0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Client received a NACK for table information recovery request for specified logical slot and table."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-INVRECRESP

SEVERITY: Warning
FORMAT: "Lslot=%d Resp Expected For %s, %d got for %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Client received the table information recovery response for a table different from what it requested."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-7-STBAVAIL

SEVERITY: Information
FORMAT: "Standby available for %s request"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Client received a NACK from the Active DB Server indicating that the request needs to be sent to Standby DB Server as well as the Standby DB Server is available to receive requests from the DB Client."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-5-REGSTSNACK

SEVERITY: Warning
FORMAT: "Received NACK from %s for %s, reason=ox%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Client received a NACK from the Active DB Server for the specified request for the specified reason."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2C-7-REG

SEVERITY: Information
FORMAT: "Sending Registration %s"
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: "The DB Client is sending the registration begin/end request as specified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS "diskdb"

DB2S-4-DBSVR_COMEP

SEVERITY: Error
FORMAT: "Error 0x%x instantiating DB Server Communication Port"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "The DB Manager Server module has failed to instantiate an IPC message queue. This could be due to shortage of memory or bad image or memory corruption or hardware problem. This results in resetting the card."
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."

DB2S-3-DBSVR_TASK_SPAW

SEVERITY: Minor Alert
FORMAT: "DBSVR Error 0x%x in spawning task %s."
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "DB Manager module failed to spawn subtask while the controller card is coming up. This results in resetting the controller card."
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."

DB2S-5-DBSVR_SEM_FAIL

SEVERITY: Warning
FORMAT: "DBSVR function %s errno = 0x%x while %s 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Manager module failed to create/take/give a semaphore. This could be due to corruption of semaphore structures or internal error. The consequences of this problem depends on the activity during which this problem occured. This may result in a Service Module failing to comeup or a provisioning request failure. If this problem occurs either on an Active PXM or on a Standby PXM while Standby PXM is coming up, the Standby PXM will fail to comeup."
RECOMMENDED ACTION: "Reset the PXM."
REQUIRED INFO: "Take a hot dump of the PXM. Save the event logs, error logs and the hot dump."

DB2S-4-DBSVR_EPHNDLR

SEVERITY: Error
FORMAT: "Error 0x%x in attaching the msg handler to DBSVR epid 0x%x"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "DB Manager module failed to initialize an IPC message queue. This could be due to bad image or memory corruption or hardware problem. This results in resetting the card."
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."

DB2S-5-DBSVR_MEM_FAIL

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

DB2S-4-DBSVR_SHMAPI

SEVERITY: Error
FORMAT: "Error 0x%x on call to %s"
FLAG: Write to Bram
THROTTLING: One Tick
EXPLANATION: "DB Manager module has got an error when called an SHM API function. This could be due to lack of IPC buffers, memory corruption or error internal to SHM. The consequences of this error depend on when this happend. If this error occured on Active controller card when Standby controller card is coming up, the Standby controller card fails to come up. If this error occured when provisioning is attempted, the provisioning request fails. If this error occured when a service module is coming up, the service module fails to come up."
RECOMMENDED ACTION: "Call TAC"
REQUIRED INFO: "Save event logs, error logs, IPC buffer information."

DB2S-5-DBSVR_IPC_FAIL

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

DB2S-4-DBSVR_DOS_FAIL

SEVERITY: Error
FORMAT: "%sError 0x%x in %s %d, %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager failed to access files on hard disk. This could be due to corrupted files or internal error or bad disk. The consequences of this error depends on the state of the system and source of the error. If this error is observed while accessing configuration files while a Service Module is coming up, then, the Service Module may fail to come up. If this error occurs during provisioning on a Service Module, the provisioning fails. If this error occurs on an Active/Standby PXM while Standby PXM is coming up and performing the disk synchronization, the Standby PXM fails to come up."
RECOMMENDED ACTION: "If this problem occurs while accessing configuration files in DDB2 directory on a Standby PXM and affects a Service Module bring up or Standby PXM bring up, clear the Standby PXM disk using sysClrallcnf from shellconn. If this problem occurs on an Active PXM and the Standby PXM is ready to take over as Active, perform a switchover and clear the configuration on the new Standby PXM disk using sysClrallcnf shellconn command. If this problem persists even after resetting the problem card, replace the hard disk card and retry. If this error occurs while accessing files in other replicated directories, viz., CFW, CSCT, ERPM etc, removed the affected file and try to download the file."
REQUIRED INFO: "Upload the problem file to a workstation, collect the event logs and error logs. Also, collect the directory listing of the directory where the problem file resides."

DB2S-7-DIRDELETE

SEVERITY: Information
FORMAT: "Deleted %s successfully"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Server deleted the specified directory."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-4-DBSVR_RECVMSG

SEVERITY: Error
FORMAT: "Error 0x%x receiving IPC message on DB Server Port"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager module received a NULL message. This should never have happend unless there is a memory corruption or severe internal error or hardware problem. The consequences of this error depends on the type of the message that was corrupted. It may result in Standby PXM or Service Module failure to come up or failing the provisioning request."
RECOMMENDED ACTION: "If this error occurs on Active PXM persistently, try to switchover to Standby PXM if available or reset the Active PXM. If this error occurs on a Standby PXM and is persistent, rebuild the Standby PXM. If this problem persists even after resetting the card, try with a different card."
REQUIRED INFO: "Take a hot dump of the PXM on which this error is observed."

DB2S-5-DBSVR_GEN_FAIL

SEVERITY: Warning
FORMAT: "%s%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "This event is logged after logging other errors and failures indicating the type of activity that failed. The consequences are determined by the activity that has failed and are covered by those of the preseding events that are logged by the DB Manager module."
RECOMMENDED ACTION: "Follow the actions recommended for other errors that occured in DB Manager module preceding to this error."
REQUIRED INFO: No Required Info

DB2S-4-DBSVR_INVEVTGRP

SEVERITY: Error
FORMAT: "Invalid DB Server event group <%d>, arg = 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager module received a message with unknown or unsupported event group. This problem could occur if the IPC message that is received by the DB Manager module has been corrupted. The consequences of this error depend on the type of the message. If the message has been sent by a Service Module during its coming up, the Service Module may fail to come up. If this message has been received on the Active or Standby controller card when the Standby controller card is coming up, it fails to come up. If this message has been received on the Active controller card due to provisioning, the provisioning fails. If this message has been received by the Standby controller card due to provisioning, it doesn't affect the provisioning."
RECOMMENDED ACTION: "Call TAC to determine whether the problem is with the sender or the receiver."
REQUIRED INFO: "Take a hot dump of the controller card. Save event logs, error logs and the core dump."

DB2S-4-DBSVR_VER_NOTSU

SEVERITY: Error
FORMAT: "Message version %x not supported. Current version is %x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Manager module received a message with unknown or unsupported DB protocol version. This problem could occur if the IPC message that is received by the DB Manager module has been corrupted. The consequences of this error depend on the type of the message. If the message has been sent by a Service Module during its coming up, the Service Module may fail to come up. If this message has been received on the Active or Standby controller card when the Standby controller card is coming up, it fails to come up. If this message has been received on the Active controller card due to provisioning, the provisioning fails. If this message has been received by the Standby controller card due to provisioning, it doesn't affect the provisioning."
RECOMMENDED ACTION: "Call TAC to determine whether the problem is with the sender or the receiver."
REQUIRED INFO: "Take a hot dump of the controller card. Save event logs, error logs and the core dump."

DB2S-5-DBSVR_CTCAPI

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

DB2S-6-PSEURESV

SEVERITY: Notice
FORMAT: "Pseudo reserving the slot %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Server is pseudo reserving the specified logical slot upon receiving first DB request from that slot."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-4-EVTPROCFAIL

SEVERITY: Error
FORMAT: "Event Processing Failed Event=%s, Reason=%s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "The DB Manager module has failed to process the specified system event. Usually, this EVTPROCFAIL event is preceded by one or more errors events logged indicating why processing the specified event has failed. The consequences of failure to process the specified system event depends on the type of the system event. If this event is logged when processing a system event for cleaning up configuration of a Service Module slot, the Service Module slot may become unusable."
RECOMMENDED ACTION: "Using the errors logged preceding this event, determine why the processing the specified system event has failed and take the actions recommended for those respective events."
REQUIRED INFO: "Take a hot dump. Save the core file, event logs and error logs."

DB2S-4-DBSVR_BAD_DATA

SEVERITY: Error
FORMAT: "DBSVR bad data in %s Bad data 0x%x, 0x%x"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Manager module received bad data through a message or found one of its internal data corrupted. This could be due to either the IPC message that was received by the DB Manager was corrupted or DB Manager's internal data structured were corrupted. If this problem occurs while Standby controller was coming up, the Standby controller fails to come up. If this problem occurs while a Service Module is coming up, the Service Module fails to come up. If this problem occured while provisioning, the provisioning fails."
RECOMMENDED ACTION: "Reset the problem card earliest possible."
REQUIRED INFO: "Take a hot dump. Save the core file, event logs and error logs."

DB2S-4-DBSVR_BAD_REC

SEVERITY: Error
FORMAT: "DBSVR Bad record %s 0x%x, %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager module detected that the specified record in the specified table has been corrupted by using checksum validation or some such means. The configuration corresonding to these records will be missing on the controller or on the Service Module. The consequences of this missing configuration depends on the type of the missing configuration."
RECOMMENDED ACTION: "Switchover to Standby PXM to check if these records are good on Standby PXM. If these records are not corrupted on Standby, the old Active PXM would recover the corrupted records. If these records are corrupted on the new Active PXM also, then, restore the configuration from the latest saved configuration. If many of these events are observed, it could be due to bad disk and it is highly recommended to change the hard disk back card."
REQUIRED INFO: "Take core dump, save the configuration and collect event logs and error logs."

DB2S-5-DBSVR_VAL_FAIL

SEVERITY: Warning
FORMAT: "DBSVR Validation failed in %s errno = 0x%x %s 0x%x 0x%x"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "Db server validation task failed "
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSVR_OS_FAIL

SEVERITY: Warning
FORMAT: "%sError 0x%x %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager module encountered failure when attempting to get time of day. It has no impact or consequences. This can be ignored."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-4-DBSVR_INTERNAL_

SEVERITY: Error
FORMAT: "%sInternal failure - %s %d"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager module detected internal data structure inconsistency. This could be due to memory corruption. This error results in failing the provisioning request."
RECOMMENDED ACTION: "Reset the card."
REQUIRED INFO: "Take hot dump, the configuration and collect event and error logs."

DB2S-5-DBSVR_GEN_FAIL1

SEVERITY: Warning
FORMAT: "%s. Extra Info- %s<0x%x>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager module detected general failure condition. This event provides additional information to an already logged error. The consequences of this error depend on the actual error that has occured."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSVR_GEN_FAIL2

SEVERITY: Warning
FORMAT: "%s. Extra Info- %s<0x%x>, %s<0x%x>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager module detected general failure condition. This event provides additional information to an already logged error. The consequences of this error depend on the actual error that has occured."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSVR_GEN_FAIL3

SEVERITY: Warning
FORMAT: "%s. Extra Info- %s<0x%x>, %s<0x%x>, %s<0x%x>"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Manager module detected general failure condition. This event provides additional information to an already logged error. The consequences of this error depend on the actual error that has occured."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-DBSVR_WARNING

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

DB2S-4-DBSVR_BAD_PARAM

SEVERITY: Error
FORMAT: "%s %s. Expect <%s>, Received <%s>"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Manager module received a request with parameters that don't match with the information stored in its control structures and/or on disk. This could be due to corruption of its control structures in memory or the corruption of the IPC buffer it received or data on the hard disk. This results in failing the controller card or Service Module to come up."
RECOMMENDED ACTION: "Call TAC."
REQUIRED INFO: "Take hot dump, save the configuration and collect event and error logs."

DB2S-7-DBSVR_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-7-SKIPCHK

SEVERITY: Information
FORMAT: "INTEGRITY CHECK Integrity Skipped. Reason %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Server integrity check is skipped for the reason specified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-SKIPSLOT

SEVERITY: Information
FORMAT: "INTEGRITY CHECK Integrity Skipped for lslot %d. Reason %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Server integrity check of the specified lslot is skipped for the reason specified."
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-7-CHKCOMP

SEVERITY: Information
FORMAT: "INTEGRITY CHECK %s"
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: "DB Server integrity check has either completed successfully or skipped/failed as specified"
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DB2S-5-INVLSLOT

SEVERITY: Warning
FORMAT: "%s Received Lslot %d is invalid. Min=%d, Max=%d"
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: "DB Server API function received an invalid Lslot as one of its parameters."