MGX Error Messages, Release 5
MGX 5 Error Messages
Downloads: This chapterpdf (PDF - 2.41MB) The complete bookPDF (PDF - 3.55MB) | Feedback

Error Messages for MGX Release 5.0.00

Table Of Contents

Error Messages for MGX Release 5.0.00

New and Modified Error Messages for MGX Release 5

DDTS: snmp-ma

CB_S-5-PROXYERRORMISC

DDTS: config save restore

CUTW-5-STATIC_DEL_FAIL

DDTS: snmp-ma

MIB-7-UNKNOWNFRONTMOD

DDTS: vsi

VSIC-5-VSICGENERR

DDTS: drivers

SAR-7-GEN_INFO

DDTS: shm

SHM_-7-PXM_CBC_RDY

SHM_-7-PXM_CBC_NOT_RDY

SHM_-5-SSM_EVT_DROP

DDTS: snmp-ma

SUBA-4-FAILED_RESOLVE_

DDTS: ssi

SRPR-5-INVALID_DBID

SRPR-5-SR_IPCWARNING

SSI-5-ME_LOCKFAIL

DDTS: AAA

AAA-5-NO_AUTH_FOUND

AAA-4-INV_TRC_INDEX

AAA-4-CLI_RSP_ERR

AAA-4-INV_SVR_ID

AAA-4-DEL_EMPTY_LIST

AAA-4-INV_SVR_PTRS

AAA-4-SVR_RBLD_ERR

AAA-4-SHC_REGCOMP_ERR

AAA-4-SHC_BUF_ERR

AAA-7-SHC_LOG_TRUNC

AAA-7-SHC_USRNM_TRUNC

AAA-7-SHC_CDTYP_TRUNC

AAA-4-UNKN_SVR_TYPE

AAA-7-TACACS_ADMN_MSG

AAA-5-W_DEFAULT_PRIV

AAA-7-TIMEOUT_CHANGED

AAA-4-IE_FUNC_FAIL

AAA-4-IE_FUNC_FAIL2

AAA-4-IE_FUNC_FAIL_E

AAA-4-UNEXPECTED_VAL

AAA-4-UNEXPECTED_VAL2

AAA-4-IE_UNEXP_START

AAA-4-IE_INVALID_PARM

AAA-5-MISCNF_ENCRYPT1

AAA-5-MISCNF_ENCRYPT2

AAA-5-MISCNF_AVP_IDLE

AAA-5-MISCNF_AVP_PRIV

AAA-5-MISCNF_AVP_VAL

AAA-5-MISCNF_AVP_SUPP

AAA-5-MISCNF_AVP

AAA-5-MISCNF_INVSTAT2

AAA-5-MISCNF_INVPAP

AAA-5-MISCNF_INVSTAT3

AAA-5-MISCNF_SVR_STAT

AAA-5-MISCNF_RPM_TLNT

AAA-5-SVR_MSG_ERROR

AAA-5-ACS_AUTHOR_PRIV

AAA-5-MISCNF_MSG_SIZE

AAA-4-IE_SMALL_READ

AAA-4-IE_READ_FAIL

AAA-5-MISCNF_SVR_FLSH

AAA-4-IE_AVP_NULL_PRM

AAA-4-IE_AVP_TOOLONG

AAA-4-IE_AVP_HASH_ADD

AAA-4-IE_AVP_ZERO_LEN

AAA-4-IE_AVP_NO_UNKN

AAA-4-IE_CON_TOO_BIG

AAA-4-IE_CON_CLOSE_TO

AAA-4-IE_CON_UNAVAIL

AAA-4-IE_CON_COUNT

AAA-4-IE_CON_START_TO

AAA-4-IE_CON_CLOSE

AAA-4-IE_CON_COUNT2

AAA-4-IE_CON_RTRY_TO2

AAA-4-IE_CON_RTRY_TO

AAA-4-IE_CON_RCV_LIST

AAA-4-IE_CON_CHECK_TO

AAA-4-IE_CON_READ_BIG

AAA-4-IE_CON_ABORTSTR

AAA-4-IE_CON_FLUSH_SZ

AAA-4-IE_CON_PERSISTS

AAA-4-IE_METH_NO_ROOT

AAA-4-IE_METH_EMPTY

AAA-4-IE_METH_BAD_RSP

AAA-4-IE_METH_UNKN_P

AAA-4-IE_METH_UNKN_P2

AAA-4-IE_METH_UNKN

AAA-4-IE_METH_STAT

AAA-4-IE_METH_CISCO

AAA-4-IE_CCMODE_UNKN

AAA-4-IE_CTX_TOO_BIG

AAA-4-IE_TASK_STATE

AAA-4-IE_TASK_VALUE

AAA-4-IE_TASK_VALUE2

AAA-4-IE_SHCL_FAIL_I

AAA-4-IE_TASK_FAIL_A

AAA-4-IE_TASK_FAIL_S

AAA-4-IE_IPC_ALLOC

AAA-4-IE_IPC_ALLOC2

AAA-4-IE_IPC_SEND

AAA-4-IE_IPC_SEND2

AAA-4-IE_IPC_TO

AAA-4-IE_IPC_BIND

AAA-4-IE_IPC_EPIDFIND

AAA-4-IE_IPC_INIT

AAA-4-IE_IPC_RSP_SIZE

AAA-4-IE_IPC_RSP_BAD

AAA-4-IE_STASK_SPAWN

AAA-4-IE_STASK_FAIL_I

AAA-4-IE_STASK_TO

AAA-4-IE_STASK_RSP

AAA-4-IE_STASK_BADRSP

AAA-4-IE_STASK_RSP_TO

AAA-4-IE_TPLUS_SIZE

AAA-4-IE_PRIV_MISSING

AAA-4-IE_USERNAME

AAA-4-IE_PASSWORD

AAA-4-IE_CMD_LEN

AAA-4-IE_METH_ALLFAIL

AAA-4-IE_AUTHOR_REQ

AAA-4-IE_AUTHEN_BUFF

AAA-4-IE_CLI_INIT

AAA-4-IE_EXCPTN_STR

AAA-4-IE_SVR_IDX

AAA-4-IE_RSYNC_DONE

AAA-4-IE_RSYNC_SIZE

AAA-5-MISCNF_SVR_MSG

AAA-5-MISCNF_SVR_MSG2

AAA-5-MISCNF_AUTH_AVP

AAA-5-MISCNF_CSCO_AVP

AAA-5-MISCNF_CHALLENG

AAA-4-IE_CTX_P_BAD

AAA-4-IE_CON_P_BAD

AAA-4-IE_CTX_NOT_FREE

AAA-4-IE_CTX_DELETED

AAA-4-IE_CTX_UNAVAIL

AAA-4-IE_CTX_MISSING

AAA-4-IE_CTX_CLOSE_TO

AAA-4-IE_CTX_START_TO

AAA-4-IE_CTX_TO

AAA-4-IE_SOCKET_FLUSH

AAA-5-W_SOCKET_FLUSH

AAA-4-IE_ENCRYPT_ERR1

AAA-4-IE_BUFF_ALLOC

AAA-4-IE_SVR_WKUP_TO4

AAA-4-IE_SVR_WKUP_TO3

AAA-4-IE_SVR_WKUP_TO2

AAA-4-IE_SVR_WKUP_TO1

AAA-4-IE_SVR_DEL_TAG

AAA-4-IE_RANDOM_NUM

AAA-4-IE_MSG_CREATE_P

AAA-4-IE_NULL_STAT_P

AAA-4-IE_ABORT_MSG_SZ

AAA-4-IE_SVR_LIST

AAA-4-IE_SVR_END

AAA-7-NETWORK_DOWN

AAA-4-IE_SOCKET

AAA-4-IE_INVALID_PTR

AAA-4-IE_BUFF_P

AAA-4-IE_DUP_TID

AAA-4-IE_WRONG_TASK

AAA-4-IE_TASK_EVT_REG

AAA-4-IE_BAD_CTC_SLOT

AAA-5-W_EARLY_FAIL

AAA-5-W_EARLY_PASS

AAA-4-IE_BAD_RSPID

AAA-4-IE_AAACC_SIZE

AAA-4-IE_AAACC_VERSN

AAA-5-W_NO_STAT_SEND

AAA-5-W_THROTTLED

AAA-4-IERR_INV_NETPTR

AAA-4-IERR_INV_MSGIDX

DDTS: ANN

ANN-4-MODERR

ANN-4-ERRMSG

ANN-4-INV_PARAM

ANN-4-INV_PARAMX

ANN-4-SWERR

ANN-6-INFOLOG

ANN-4-GENERR

DDTS: ars

ARS-5-ARSERR

ARS-4-GENERR

DDTS: BCDRV

BCDR-5-DRVERR

BCDR-4-ERRMSG

BCDR-4-INV_PARAM

BCDR-4-INV_PARAMX

BCDR-4-SWERR

BCDR-6-INFOLOG

BCDR-4-GENERR

BCDR-6-TRANSTYPE

DDTS: CDMON

CDMO-5-CDMONERR

CDMO-4-IPCSENDFAIL

CDMO-4-IPCERR

CDMO-4-SWERR

CDMO-2-TASKINIT

CDMO-2-DSPMISMATCH

CDMO-6-INFOLOG

CDMO-4-GENERR

DDTS: snmp-ma

CB_S-5-MSGSENDFAILWARN

DDTS: signaling

CC-5-CC_PB_QUEUE_WAR

DDTS: VXSM_CCM

VXSM-4-CCMERR

VXSM-4-IPCSENDFAIL

VXSM-4-IPCERR

VXSM-4-SWERR

VXSM-4-MEMLOWERR

VXSM-4-MEMHIGH

VXSM-4-IPCBUFLOWERR

VXSM-4-IPCBUFHIGH

VXSM-4-PEAKCPUHIGHERR

VXSM-4-PEAKCPULOW

VXSM-4-PEAKCPUMEDERR

VXSM-4-AVGCPUHIGHERR

VXSM-4-AVGCPULOW

VXSM-4-AVGCPUMEDERR

VXSM-2-TASKINIT

VXSM-2-TASKUTILHIGH

VXSM-6-LOG

VXSM-4-GENERR

VXSM-4-MSGQLOW

VXSM-4-MSGQHIGHERR

VXSM-4-HSSHIGHERR

VXSM-4-HSSLOWERR

VXSM-4-HSSMEDERR

VXSM-4-SVCHIGHERR

VXSM-4-SVCLOWERR

VXSM-4-SVCMEDERR

DDTS: ccm

CCM-5-LOG_WARNING

DDTS: AAA

CLF-4-APPEND_INV_PTR2

CLF-4-INIT_INV_PTR4

CLF-5-FILE_CREATE_ERR

CLF-5-IFILE_WRITE_ERR

CLF-4-DIV_BY_ZERO

CLF-5-APPEND_ERR

CLF-4-INV_LENGTH

CLF-7-LDIR_CREATED

CLF-7-FILE_CREATED

DDTS: CLI

CLI-7-CLISSHLOG

CLI-4-CLISSHERR

CLI-5-SESNPURGE

CLI-7-GENERR

CLI-4-SHELLCONN_AMBIG

CLI-4-CC_BUFFER_SMALL

DDTS: clocking

CLK_-7-SSI_API_FAILED

DDTS: CLKDRV

CLKD-4-DRVERR

CLKD-4-ERRMSG

CLKD-4-INV_PARAM

CLKD-4-SWERR

CLKD-6-INFOLOG

CLKD-4-GENERR

DDTS: ccma

CCMA-7-CCMAENTEREDTASK

CCMA-7-CCMAAFTEREPID

CCMA-7-CCMADEBUG1

CCMA-7-CCMACHILDTASKSP

CCMA-7-CCMATASKIDOFCHI

CCMA-7-CCMADEBUG4

CCMA-7-CCMADEBUG5

DDTS: COT

COT-2-MOD_INIT_FAIL

COT-5-RES_ALLOC_FAIL

COT-5-RES_RELEASE_FAI

COT-4-NULL_POINTER_ER

COT-5-UNSUP_FEATURE

DDTS: cpro

CPRO-5-IRMHDDBCREATEFA

CPRO-7-IRMHDDBCREATEOK

CPRO-5-IRMHDDBTBLCREAT

CPRO-5-IRMHDDBBWTBLCRE

CPRO-5-IRMDBREGISTERFA

CPRO-7-IRMINITOK

CPRO-7-ENTEREDIRMHDDBC

CPRO-7-ENTEREDIRMHDDBC

CPRO-7-ENTEREDIRMHDDBC

CPRO-7-CPRODEBUG1

CPRO-7-CPRODEBUG2

CPRO-7-CPRODEBUG3

CPRO-7-CPRODEBUG4

CPRO-7-CPRODEBUG5

CPRO-7-CPRODEBUG6

CPRO-7-CPROHANDLECNFG

CPRO-7-CPROADDCONN

CPRO-7-CPROSENDCNTRL

CPRO-7-CPROCNTRLACKREC

CPRO-4-BULK_EVENT_FOR_

CPRO-4-TRANS_ID_DB_UPD

CPRO-4-DROP_VSI_EVENT

CPRO-4-LICENSE_MGMT

CPRO-4-LM_RESYNC_ERR

DDTS: CRML

CRML-2-MOD_INIT_FAIL

CRML-5-RES_ALLOC_FAIL

CRML-5-RES_RELEASE_FAI

CRML-5-DSP_CHAN_MODIFY

CRML-2-REDM_ADDCON_FAI

CRML-2-REDM_MODCON_FAI

CRML-2-REDM_DELCON_FAI

CRML-5-DSP_CONGESTION_

CRML-4-NULL_POINTER_ER

CRML-4-DSP_CONFIG_PARA

CRML-5-UNSUP_FEATURE

CRML-5-TOO_MANY_DIGITS

CRML-5-REDM_DELCON_WAR

CRML-4-CM_DSPAPI_ERROR

CRML-5-MULTIPLE_CHAN_W

CRML-2-NO_FURTHER_CALL

CRML-2-UNSUPP_API_CALL

CRML-2-UNSUPP_OPER_REQ

CRML-2-TERM_CLEANUP_FA

DDTS: config save restore

CSR-5-CSRERR067

CSR-5-CSRERR072

CSR-5-CSRERR090

CUTW-5-CSRERR067

DDTS: ctc

CTC-5-CDEVTRGSTRFAILE

CTC-4-CD_FATAL_ERR_GE

DDTS: DAT

DAT-2-MOD_INIT_FAIL

DAT-4-RES_ALLOC_FAIL

DAT-4-RES_RELEASE_FAI

DAT-4-NULL_POINTER_ER

DAT-5-UNSUP_FEATURE

DAT-5-TOO_MANY_DIGITS

DAT-4-RES_RESERVE_FAI

DAT-7-LOG

DAT-4-TIMER_ERROR

DAT-5-SIGNAL_EVT_NOT_

DDTS: diskdb

DB2C-4-SRVR_NOTUPG

DB2C-5-MSG_ACK

DB2S-7-DBSVR_INFO

DB2S-7-CNFCLR_UPDT

DB2S-7-DBSVR_PERSISTSI

DB2S-5-DBSVR_PERSISTSI

DDTS: drivers

DDLW-4-SAR_ERR

DDLW-4-ATM_ERR

DDLW-5-SAR_WARN

DDLW-5-ATM_WARN

DDLW-4-FR_WP_ERR

DDLW-4-FR_PORT_DB_ERR

DDLW-4-FR_PORT_CONFIG_

DDLW-4-FR_CONN_DB_ERR

DDLW-4-FR_CONN_CONFIG_

DDLW-4-FR_PHY_DB_ERR

DDLW-4-FR_PHY_ENABLE_E

DDLW-4-FR_PHY_MODIFY_E

DDLW-4-FR_IW_QNODE_DB_

DDLW-5-FR_WP_WARN

DDLW-4-WPSTATS_ERR

DDLW-7-OAM_ERR

DDTS: DIL_DSP

DIL_-1-DOWNLOAD_FAILUR

DIL_-4-INVALID_PARAM

DIL_-4-API_FAILURE

DDTS: VXSM-AGERE

DIL_-2-DM_INIT_FAIL

DIL_-5-AGERE_API_FAIL

DIL_-5-BAD_PARAM

DIL_-5-SEM_TAKE_FAILUR

DIL_-5-RESOURCE_UNAVAI

DIL_-5-CONN_PRESENT

DIL_-5-CONN_ABSENT

DDTS: DSPAPI

DSPA-6-IOP_ERR

DSPA-6-HOST_ERR

DDTS: DSPDRV

DSPD-6-ERR

DDTS: dsp

DSPK-4-ERR

DDTS: FDL

FDL-4-MODERR

FDL-4-ERRMSG

FDL-4-INV_PARAM

FDL-4-INV_PARAMX

FDL-4-SWERR

FDL-6-INFOLOG

FDL-4-GENERR

DDTS: ppugl

PPUG-4-GLTXNIDOP

PPUG-4-TSCMNMEMPOOLCRE

PPUG-4-TSCMNMEMPOOLGET

PPUG-4-TSCMNMEMPOOLREL

PPUG-4-TSCMNMEMPOOLDEL

PPUG-4-CMNMEMPOOLCREAT

PPUG-4-CMNMEMPOOLGETBU

PPUG-4-CMNMEMPOOLRELBU

PPUG-4-CMNMEMPOOLGETOW

PPUG-4-CMNMEMPOOLCHAOW

PPUG-4-CMNMEMPOOLDELPO

PPUG-4-CMNMEMPOOLRELBU

PPUG-4-GSCIMFILEIOOPEN

PPUG-4-GSCIMFILEIOCLOS

PPUG-4-GSCIMFILEIOSEEK

PPUG-4-GSCIMFILEIOREAD

PPUG-4-GSCIMFILEIOWRIT

PPUG-4-GSCIMFILEIOEOF

PPUG-4-GSCIMFILEIOFLUS

PPUG-4-GSCIMFILEIOERRI

PPUG-4-GSCIMMUTEXCREAT

PPUG-4-GSCIMMUTEXDELET

PPUG-4-GSCIMMUTEXLOCK

PPUG-4-GSCIMMUTEXUNLOC

PPUG-4-GSCIMSEMCREATE

PPUG-4-GSCIMSEMDELETE

PPUG-4-GSCIMSEMWAITONS

PPUG-4-GSCIMSEMTRYWAIT

PPUG-4-GSCIMSEMRELEASE

PPUG-4-GSCIMTHMCREATE

PPUG-4-GSCIMTHMGETTHDI

PPUG-4-GSCIMTHMSUSPEND

PPUG-4-GSCIMTHMRESUME

PPUG-4-GSCIMTHMDESTROY

PPUG-4-TSMEMPOOLCREATE

PPUG-4-TSMEMPOOLGETBUF

PPUG-4-TSMEMPOOLRELBUF

PPUG-4-TSMEMPOOLDELPOO

PPUG-4-TSMEMPOOLRELBUF

PPUG-4-CNGSTMGMTTASKPO

PPUG-4-CNGSTMGMTCMNPOO

PPUG-4-CNGSTMGMTCMNPOO

PPUG-4-CNGSTMGMTTASKPO

PPUG-4-MMGETUSERIDINFO

PPUG-4-MMRMUSERIDINFON

PPUG-4-MMRELALLIDALLOC

PPUG-4-MMADDBUFTOUSERI

PPUG-4-MMRELBUFFRMUSER

PPUG-4-MMAUDMEMFREEFUN

PPUG-4-MMINIT

PPUG-4-MMDESTALLCMNPOO

PPUG-4-MMDESTALLTASKPO

PPUG-4-TMSTARTTIMER

PPUG-4-TMSTOPTIMER

PPUG-4-TMSTOPALLTIMERS

PPUG-4-TMGETTIMERBUFF

PPUG-4-MMSETCMNPOOLSTK

PPUG-4-MMSETCMNPOOLBUF

PPUG-4-MMENACMNPOOLUSA

PPUG-4-MMDISCMNPOOLUSA

PPUG-4-MMGETCMNPOOLSTK

PPUG-4-MMGETCMNPOOLBUF

PPUG-4-MMREPORTCMNPOOL

PPUG-4-MMREPORTCMNPOOL

PPUG-4-MMSETTASKPOOLST

PPUG-4-MMSETTASKPOOLBU

PPUG-4-MMENATASKPOOLUS

PPUG-4-MMDISTASKPOOLUS

PPUG-4-MMGETTASKPOOLST

PPUG-4-MMGETTASKPOOLBU

PPUG-4-MMREPORTTASKPOO

PPUG-4-MMREPORTTASKPOO

PPUG-4-MMSETBUFALLOCSI

PPUG-4-MMSETCMNPOOLAUD

PPUG-4-MMGETBUSYUSERID

PPUG-4-MMGETUSERIDSTAT

PPUG-4-MMRELALLUSERIDA

PPUG-4-TMDELETETIMER

PPUG-4-TMIDLISTINIT

PPUG-4-TMINIT

PPUG-4-TMLISTCREATE

PPUG-4-TMLISTDELETE

PPUG-4-TMDESTROYALLTIM

PPUG-4-TMSPAWNTIMERSER

PPUG-4-TMINVOKETIMEREX

PPUG-4-SMCREATESOCKET

PPUG-4-SMBINDSOCKET

PPUG-4-SMCONNECTSOCKET

PPUG-4-SMLISTENSOCKET

PPUG-4-SMACCEPTSOCKET

PPUG-4-SMIOCTLSOCKET

PPUG-4-SMSENDTO

PPUG-4-SMRECVFORM

PPUG-4-SMSEND

PPUG-4-SMRECV

PPUG-4-SMSETSOCKOPT

PPUG-4-SMGETSOCKOPT

PPUG-4-SMGETSOCKNAME

PPUG-4-SMGETPEERNAME

PPUG-4-SMCLOSESOCKET

PPUG-4-SMINETADDR

PPUG-4-SMGETHOSTNAME

PPUG-4-SMHOSTGETBYNAME

PPUG-4-SMTLMINIT

PPUG-4-SMTLMSETTPTLNKI

PPUG-4-SMTLMGETTPTLNKI

PPUG-4-SMTLMDELTPTLNKI

PPUG-4-SMTLMSETTPTLNKK

PPUG-4-SMTLMGETTPTLNKK

PPUG-4-SMTLMDELTPTLNKK

PPUG-4-SMCONVERTUDPTPT

PPUG-4-STMSTRCPY

PPUG-4-STMSTRNCPY

PPUG-4-STMSTRCAT

PPUG-4-STMSTRNCAT

PPUG-4-STMSTRLEN

PPUG-4-STMSTRCMP

PPUG-4-STMSTRNCMP

PPUG-4-STMATOI

PPUG-4-STMITOA

PPUG-4-STMSTRCMPI

PPUG-4-STMSTRNCMPI

PPUG-4-STMSTRCHR

PPUG-4-STMSTRRCHR

PPUG-4-STMSTRPBRK

PPUG-4-STMSTRSTR

DDTS: h248cnf

H248-4-H248CNF_GENERR

H248-7-H248CNF_GENINFO

H248-1-FATAL_ERR

DDTS: hw-poll

HMM_-4-HV_DTE_WR_ERR

HMM_-4-HV_CAM_OP_ERR

DDTS: ima

IMA-6-MSG_GRP_RX_IMA_

DDTS: irm

IRM-5-IRMERR

IRM-4-IPCSENDFAIL

IRM-4-IPCERR

IRM-4-SWERR

IRM-1-TASKINIT

IRM-2-PROXY_TASKINIT

IRM-2-RCM_TASKINIT

IRM-6-LOG

IRM-4-GENERR

DDTS: IUA

IUA-4-IUAINITFAILED

IUA-7-ASINACTIVE

IUA-7-ASPENDING

IUA-4-IUAFAILEDTOREST

IUA-5-IUAGWINVALIDEVE

IUA-4-IUAIRMUPDATEFAI

IUA-4-IUAIRMCBFAIL

IUA-4-IUARECALLOCFAIL

IUA-4-IUARECFREEFAILE

IUA-7-VXSMSWITCHOVER

IUA-4-TIMERCREATEFAIL

IUA-4-TIMERSTARTFAIL

IUA-4-TIMERSTOPFAIL

IUA-5-IUAMSGPROCESSFA

IUA-5-IUAASCREATEINST

IUA-5-IUAASCREATEASSO

DDTS: lim

LIM-4-LIM_GENERR

LIM-7-LIM_GENINFO

DDTS: license

LMC-4-EP_FAIL

LMC-4-ERROR_RET

LMC-5-WAIT_LOOP

LMC-5-INVALID_MSG

LMC-5-INVAL_PTR

LMC-4-INVAL_STATE

LMC-4-SEND_FAIL

LMC-4-RCV_FAIL

LMC-4-RCV_NACK

LMC-4-ERR_VAL

LMC-4-AUDIT_FAIL

LMC-5-TIMER_TERM

LMC-7-EVT_INFO

LMC-5-STAT_CHG

LMC-7-STAT_DIS

DDTS: license

LICE-3-FAILED_DBCREATE

LICE-3-FAILED_TBLCREAT

LICE-3-FAILED_DBREGIST

LICE-3-FAILED_REVCHANG

LICE-3-FAILED_DBWRITE

LICE-3-FAILED_DBREAD

LICE-3-FAILED_DBNXTREA

LICE-3-FAILED_FUNCTION

LICE-7-ALLOC_STDBY

LICE-7-ALLOC_SEC

LICE-7-FAIL_ALLOC_SEC

LICE-7-ALLOC_SLOT

LICE-7-REL_SEC

LICE-7-FAIL_REL_SEC

LICE-7-REL_STDBY

LICE-7-REL_SLOT

LICE-7-POOL_LOG

LICE-7-INSTALL_LOG

LICE-7-NEVER_LICENSED

LICE-7-SHELFID_NULL

LICE-7-XFR_GEN_OK

LICE-4-XFR_GEN_ERR

LICE-7-DECRYPT_OK

LICE-4-DECRYPT_ERR

LICE-4-LIC_CHECKSUM_ER

LICE-7-EXPIRY_ALERT

LICE-7-GRACE_ALERT

LICE-4-WR_BKPL_NVRAM

LICE-4-RD_BKPL_NVRAM

LICE-3-CTC_EXCEPTION

LICE-3-COMEPCREATEFAIL

LICE-3-CNTRLMSGHDLRFAI

LICE-3-COMEPATTACH_FAI

LICE-7-ILLEGAL_TRANSTI

LICE-5-SYSINVALID

LICE-5-UPGRADE_SEQNUM

LICE-5-UNEXPECTED_SEQN

LICE-5-UPD_METHOD

LICE-5-INVALID_LICS

LICE-5-DISCREPENCY_POO

LICE-7-FIX_OK_DISCREPE

LICE-5-FIX_ERR_DISCREP

LICE-5-GENERALWARNING

LICE-5-WARNING_INTERNA

LICE-5-WARNINGWITHDATA

LICE-5-PARAMINVALID

LICE-4-GENERALERROR

LICE-4-ERRORWITHDATA

LICE-3-BKPLIDLMISMATCH

LICE-3-BKPLSEQNUM

LICE-5-DATAXFERHNDLR

LICE-5-UNKNOWNREQUEST

LICE-5-DISC_POOL_RAM

LICE-5-DISC_ALLOC_RAM

LICE-5-DISC_SLOT_RAM

LICE-5-DISC_SLOT_USAGE

LICE-5-UNHANDLED_REQ

LICE-5-SEND_REQ_FAIL

LICE-5-NOTAVAIL_XFR

LICE-5-METHOD_UNKNOWN

LICE-5-REL_SLOT_ERR

LICE-5-REL_ERROR_REJ

LICE-5-REL_1TON

LICE-5-ALLOC_SLOT_ERR

LICE-5-ALLOC_SLOT_EX_E

LICE-5-DELETE_LIC_ERR

LICE-7-REL_UNRESERVED

LICE-7-AUDIT_INACTIVE

LICE-5-SLOT_LIC_EXPIRE

LICE-5-SLOT_IN_GRACE

LICE-5-GRACE_START

LICE-7-LICS_ALARM_CLEA

LICE-7-BKPL_REKEYED

LICE-7-BKPL_TBL_UPD

LICE-7-POOL_REC_CREATE

LICE-7-AUDIT_LOG

LICE-7-AUDIT_LOGWITHDA

LICE-7-AUDIT_CLIENT_RE

LICE-7-INFO_LOGWITHDAT

LICE-5-AUDIT_WARNING

LICE-5-SRVR_OPR_STATUS

LICE-7-LMS_LOGINFO

DDTS: sys/uplink

LMI-4-EPID_ERR

LMI-5-SEM_ERR

LMI-5-SET_CNFG

LMI-5-GEN_ERR

LMI-5-CTC_STATE_ERR

LMI-4-TIMEOUT_ERR

LMI-4-TIMER_CREATE_ER

DDTS: snmp-ma

MAST-5-INVALID_BKPL_TY

DDTS: MCCI

MCCI-2-MOD_INIT_FAIL

MCCI-2-MOD_RESET_FAIL

MCCI-4-INTERNAL_ERROR

MCCI-4-INVALID_PARAMET

MCCI-4-UNSUPPORTED_API

MCCI-5-RES_MGMT_FAIL

MCCI-5-STREAM_MGMT_FAI

MCCI-5-TOPOLOGY_FAIL

DDTS: mcrs

MCRS-4-GEN_ERR

MCRS-7-GEN_INFO

MCRS-4-PROTO_ERR

DDTS: feeder-lmi

LMI-7-EXT_API_ERR_EVE

DDTS: snmp-ma

MIB-5-ENTITY_NO_BACKP

MIB-5-UNKNOWN_BKPL_CA

DDTS: diag

DIAG-7-LOG

DIAG-4-ERROR

DDTS: ccma

OAM-7-LOG

OAM-4-ERROR

DDTS: mrapi_if

MRAP-4-GEN_ERR

MRAP-7-GEN_INFO

MRAP-1-FATAL_EVT

MRAP-3-MINOR_EVT

DDTS: atmsig

NCDT-7-OUTSTANDING_CLK

DDTS: pxm-connmgm

PHPI-5-SEMERR

PHPI-4-UNREGSM_ERR

PHPI-4-VERMISMATCH_ERR

PHPI-4-CREFLIMIT_ERR

PHPI-4-SPIPOOLGET_ERR

PHPI-4-MEM_ERR

PHPI-4-DEALLOC_ERR

PHPI-4-ALLOC_ERR

PHPI-4-INVSLOT_ERR

PHPI-4-VERSIONNOTSUPP_

PHPI-4-CFGMISMATCH_ERR

PHPI-7-CREFNOTPRESENT

PHPI-4-DBDEL_ERR

PHPI-4-RESYNCH_ERR

PHPI-4-SCHEDULE_TO_ERR

PHPI-4-MSGSEND_ERR

PHPI-4-INIT_ERR

PHPI-4-INVALIDMSGRCVD_

PHPI-4-RMCREFCNTR_ERR

PHPI-4-GEN_ERROR_API

PHPI-4-SPI_ERROR

PHPI-4-CREF_DB_ERROR

PHPI-4-CREF_PROG_ERROR

PHPI-7-MISMATCH_INFO

PHPI-7-GEN_INFO

PHPI-2-SYNCRAMERR

PHPI-5-SYNCRAMEV

PHPI-7-PSLOT_INFO_ERRO

PHPI-7-INFO_LOG

DDTS: vsi

VSI_-4-PRMMajorErr

VSI_-3-PRMMinorErr

VSI_-6-PRMInfoLog

DDTS: vsi

VSIC-5-VSICGENERR

VSIC-5-VSICPROTERR

VSIC-5-VSICSYSERR

VSIC-5-VSICINTRNLERR

VSIC-2-VSIMAJORERR

VSIS-5-VSISERR

VSIS-5-SCTINVALIDVCERR

VSIS-5-SCTINVALIDSERVC

VSIS-4-DRIVERFAIL

VSIS-5-DALFAIL

VSIS-5-HWPROGFAIL

VSIS-4-SSIFAIL

VSIS-4-ADDVTOAMCONFAIL

VSIS-5-RAMSYNC

VSIS-5-GENERR

VSI_-5-VSIRMERR

VSI_-4-RM_ERROR

VSI_-7-RM_EVENT

DDTS: PM

PM-4-MODERR

PM-4-ERRMSG

PM-4-INV_PARAM

PM-4-INV_PARAMX

PM-4-SWERR

PM-6-INFOLOG

PM-4-GENERR

DDTS: megaco

PPU-1-PPCSPAWNFAILED

PPU-1-STACKSPAWNFAILE

PPU-4-TOPPUSYNCNULLPA

PPU-4-TOPPUSYNCZEROLE

PPU-4-TOPPUSYNCINVAPI

PPU-4-TOPPUSYNCCALLFA

PPU-4-TOPPUSYNCTIMEOU

PPU-4-ESPIPEFAILED

PPU-4-HSSAPIBEFOREINI

PPU-4-ESINVALIDAPIID

PPU-4-SYNCRESPDISCARD

DDTS: ccma

OAM-5-WARN

DDTS: rdm

RDM-2-INIT_FAIL

RDM-2-RCV_MSG_FAIL

RDM-2-RCV_MSG_NULL

RDM-7-INFO

RDM-3-ILLEGAL_MSG

RDM-2-RDT_ADD_PORT_FA

RDM-2-RDT_ADD_FUNC_FA

RDM-2-FAIL_2Q_MSG

RDM-2-WRITE_LSEEK_FAI

RDM-2-FILE_WRITE_FAIL

RDM-2-READ_LSEEK_FAIL

RDM-2-FILE_READ_FAIL

RDM-2-DB_FILE_WRITE_F

RDM-2-DB_FILE_OPEN_FA

RDM-2-DB_FILE_READ_FA

RDM-3-DELETE_HD_INVAL

RDM-3-HD_DELETE_DB_FA

RDM-3-RAM_DELETE_DB_F

RDM-3-CLEANUP_DB_FAIL

RDM-2-FAIL_TO_OPEN_FI

RDM-2-UPDATE_HD_INVAL

RDM-2-READ_HD_INVALID

RDM-2-COMIT_HD_INVALI

RDM-2-PEER_DB_FAIL

RDM-2-MKDIR_FAIL

RDM-2-TBLCREATE_OUT_O

RDM-2-PEER_TBL_FAIL

RDM-3-PEER_ENTRY_CREA

RDM-2-PEER_ENTRY_UPDA

RDM-2-ENTRY_TABLE_SEM

RDM-2-DELETING_NON_EX

RDM-2-DELETING_NON_EX

RDM-2-DELETING_NON_EX

RDM-2-COMIT_OUT_OF_ME

RDM-2-FAIL_TBLCREATE_

RDM-2-PEER_DB_EXISTS_

RDM-2-PEER_TBL_EXISTS

RDM-2-REM_DB_EXISTS_A

RDM-2-REM_TBL_EXISTS_

RDM-2-COMIT_MSG_CKSUM

RDM-2-NULL_ADDR

RDM-2-PEER_COMIT_STAR

RDM-2-PEER_COMIT_CONT

RDM-2-PEER_COMIT_MISS

RDM-2-REM_COMIT_START

RDM-2-REM_COMIT_CONT_

RDM-2-REM_COMIT_MISSI

RDM-2-ILLEGAL_COMIT_M

RDM-3-PEER_CREATE_DB_

RDM-3-PEER_CREATE_TBL

RDM-3-PEER_CREATE_ENT

RDM-3-PEER_DELETE_DB_

RDM-3-PEER_DELETE_TAB

RDM-3-PEER_DELETE_ENT

RDM-2-PEER_COMIT_ENTR

RDM-3-REM_CREATE_DB_F

RDM-3-REM_CREATE_TBL_

RDM-3-REM_CREATE_ENTR

RDM-3-REM_DELETE_DB_F

RDM-3-REM_DELETE_TABL

RDM-3-REM_DELETE_ENTR

RDM-2-REM_COMIT_ENTRY

RDM-3-SEND_PEER_CREAT

RDM-3-SEND_PEER_CREAT

RDM-3-SEND_PEER_CREAT

RDM-3-SEND_PEER_DELET

RDM-3-SEND_PEER_DELET

RDM-3-SEND_PEER_DELET

RDM-2-SEND_PEER_COMIT

RDM-3-REM_RAM_CREATE_

RDM-3-REM_RAM_CREATE_

RDM-3-REM_RAM_CREATE_

RDM-3-REM_RAM_DELETE_

RDM-3-REM_RAM_DELETE_

RDM-3-REM_RAM_DELETE_

RDM-2-REM_RAM_UPDATE_

RDM-2-REM_RAM_READ_EN

RDM-2-REM_RAM_COMIT_E

RDM-3-SEND_REM_RAM_CR

RDM-3-SEND_REM_RAM_CR

RDM-3-SEND_REM_RAM_CR

RDM-3-SEND_REM_RAM_DE

RDM-3-SEND_REM_RAM_DE

RDM-3-SEND_REM_RAM_DE

RDM-3-REM_HD_CREATE_D

RDM-3-REM_HD_CREATE_T

RDM-3-REM_HD_CREATE_E

RDM-3-REM_HD_DELETE_D

RDM-3-REM_HD_DELETE_T

RDM-3-REM_HD_DELETE_E

RDM-2-REM_HD_UPDATE_E

RDM-2-REM_HD_READ_ENT

RDM-3-SEND_REM_HD_CRE

RDM-3-SEND_REM_HD_CRE

RDM-3-SEND_REM_HD_CRE

RDM-3-SEND_REM_HD_DEL

RDM-3-SEND_REM_HD_DEL

RDM-3-SEND_REM_HD_DEL

RDM-2-PEER_HD_UPDT_AN

RDM-2-SEND_PEER_UPDT_

RDM-2-SEND_REM_RAM_UP

RDM-2-SEND_REM_RAM_RE

RDM-2-SEND_REM_HD_UPD

RDM-2-SEND_REM_HD_REA

RDM-2-SEND_REM_RAM_VA

RDM-2-SEND_REM_HD_VAL

RDM-2-SYNC_INIT_TABLE

RDM-2-FM_PEER_WR_FAIL

RDM-2-FM_SRC_FILE_CRE

RDM-2-FM_DST_FILE_CRE

RDM-2-FM_SRC_FILE_OPE

RDM-2-FM_DST_FILE_OPE

RDM-2-FM_DST_FILE_WRI

RDM-2-DBM_FM_COPY_FAI

RDM-2-SYNC_FAIL_CB_CO

RDM-2-SYNC_FAIL_L_2_P

RDM-2-SYNC_CLEAN_TABL

RDM-2-SYNC_GET_PEER_D

RDM-2-SYNC_REBUILD_TA

RDM-2-SYNC_PEER_UNBLO

RDM-3-FAIL_CREATE_HD_

RDM-3-FAIL_CREATE_RAM

RDM-3-CONV_NULL_ENTRY

RDM-2-REM_UNTAR_FAIL

RDM-3-FAIL_TO_SPAWN_C

RDM-2-SYNC_PEER_RESTO

RDM-2-FAIL_TO_SPAWN_D

RDM-2-PEER_CB_FN_FAIL

RDM-2-UPGRADE_MISMATC

RDM-2-DNGRADE_MISMATC

RDM-2-SYNC_SAVE_TABLE

RDM-2-SYNC_RESTORE_TA

RDM-2-SYNC_REMOVE_OLD

RDM-2-UPGD_OUT_OF_MEM

RDM-2-HD_CREATE_DB_ON

RDM-2-HD_CREATE_DB_ON

RDM-2-CREATE_RAM_DB_F

RDM-2-HD_CREATE_TABLE

RDM-2-HD_CREATE_TABLE

RDM-2-RAM_CREATE_TABL

RDM-2-CREATE_ENTRY_FA

RDM-3-DELETE_ENTRY_ON

RDM-3-SET_VALIDBIT_FO

RDM-2-REGISTER_DB_WIT

RDM-2-UNREGISTER_DB_W

RDM-7-INFOLOG

RDM-2-HD_UPDATE_ENTRY

RDM-2-INVALID_ARGUMEN

RDM-2-LAUNCH_STATICDB

RDM-2-ILLEGUAL_DISKTB

RDM-2-APP_CALLBK_EXEC

RDM-2-APP_CALLBK_FAIL

RDM-2-DB_DATA_SHARE_F

RDM-2-UPGRADE_GENERR

RDM-2-DB_EXCEEDED_LIM

RDM-2-EXCEEDED_MAX_EN

DDTS: irm

RDT-4-RDT_GENERR

RDT-4-SERVER_TABLE_SE

RDT-4-CLIENT_TABLE_SE

RDT-4-TX_SEM

RDT-4-GET_TXID_FAIL

RDT-4-TX_ERR

RDT-4-RCV_MSG_NULL

RDT-4-FWD_Q_ERR

RDT-4-FAIL_TO_SPAWN_S

RDT-4-OUT_OF_TASKS

RDT-4-CORRUPTED_TXID

RDT-4-MSG_ALLOC_FAIL

RDT-4-MSGQ_OVERFLOW

DDTS: irm

RFM-2-ADD_PORT_FAILED

RFM-2-INIT_FAIL

RFM-2-EP_CREATE_FAIL

RFM-2-EP_ATTACH_FAIL

RFM-2-ALLOC_FAIL

RFM-2-RCV_MSG_NULL

RFM-2-ILLEGAL_MSG

RFM-2-WRITE_FAIL

RFM-2-RDT_ASYNC_FAIL

RFM-2-OUT_OF_FDPS

RFM-2-OUT_OF_MEMORY

RFM-2-SEM_ERROR

RFM-2-WR_OVERRUN

RFM-2-CREATE_FAIL

RFM-2-DELETE_FAIL

RFM-2-OPEN_FAIL

RFM-2-CLOSE_FAIL

RFM-2-READ_FAIL

RFM-2-RENAME_FAIL

RFM-4-TID_NOT_IN_LIST

RFM-7-RENAME_EXISTING

RFM-4-INVALID_FILENAM

RFM-4-INVALID_FLAG

RFM-4-FILE_NOT_EXIST

RFM-4-INVALID_FDP

RFM-4-REMOTE_SERVICE_

RFM-4-CKSUM_FAIL

DDTS: alarms

ZAM-4-DATAPATHCHECK

DDTS: RSVP

RSVP-2-INIT_FAIL

RSVP-4-INVALID_IRM_OP

RSVP-4-HD_TBL_FAIL

RSVP-4-HD_ENTRY_CREATE

RSVP-4-IRM_COMMIT_FAIL

DDTS: rpm

RVT-4-SLOT_ERROR

RVT-5-DB_UN_INITIALIZ

RVT-5-DISK_UPD_ERROR

DDTS: shm

SCM-4-CD_FATAL_ERR_GE

SCM-5-SCM_MSG_DRPD

DDTS: SCTP

SCTP-4-SCTPINITFAILED

SCTP-5-SCTPASSOCINACTI

SCTP-5-SCTPASSOCWRONGS

SCTP-4-SCTPCHUNKINITFA

SCTP-4-SCTPCHUNKALLOCF

SCTP-4-SCTPCHUNKFREEFA

SCTP-4-TIMERCREATEFAIL

SCTP-4-TIMERSTARTFAIL

SCTP-4-TIMERSTOPFAIL

SCTP-5-SCTPMSGPROCESSF

DDTS: sds

SDS-5-IPC_FREE_ERR

SDS-5-IPC_ALLOC_FAIL

SDS-5-GET_ENT_DATA_ER

SDS-5-INVALID_RQ

SDS-5-IPC_REPLY_FAIL

SDS-5-GET_ENT_FAIL

SDS-5-EPID_FAIL

SDS-5-CTC_OP_FAIL

SDS-5-INV_INP

SDS-5-INV_IPC_DATA

DDTS: shm

SHM_-4-CD_DEAD_IGNORED

SHM_-7-STBY_ROLE_DROP

SHM_-7-STBY_SYNC_ERR

SHM_-5-CBM_SPEED_INCOM

SHM_-7-CD_STATE_INFO

SHM_-7-GENERR

SHMA-4-OBJ_DECODE_FAIL

SHMA-4-INV_MSG_TYPE2

SHMA-4-DUPLICATE_OBJS

SHMA-7-INFO_NOT_FULL

SHMA-7-REMOTE_BC_RMV

SHMA-7-BACKCARD_RES_RP

SHMA-7-REMOTE_BC_RES_R

SHMA-7-API_RCON_REPORT

SHMA-2-RCON_INSERT

SHMA-2-RCON_REMOVE

DDTS: snmp-sa

MIB-5-IPC_ALLOC_FAIL

MIB-5-IPC_FREE_FAIL

MIB-5-WARN

MIB-5-SEM_OP_FAIL

MIB-5-INV_LENGTH

MIB-4-RESP_ERR

SUBA-5-INVALID_INDEX

DDTS: pxm-connmgm

SPI-4-SDRV_PATH_PROG_

SPI-4-SDRV_CONNADDITI

SPI-4-SDRV_POOLGETSET

SPI-5-CONNREF_STATE

DDTS: srm

SRM-7-DEFAULT_T3_CFG_

DDTS: infra

SSH-4-ERR_EVT

SSH-6-SPCL_EVT

SSH-7-INFO_EVT

DDTS: ssi

DTAP-5-TASK_LOCK

SRPR-7-GENERR

SRPR-5-INVALID_PARM

SRPR-5-MSG_PURGE

SRAP-7-GENERR

SSI-5-CHNK_SHRINK_ERR

SSI-4-CHNK_INT_ERROR5

DDTS: SVC

SVC-4-SVCINITFAILED

SVC-5-SVCGWINACTIVE

SVC-5-SVCGWWRONGSTATE

SVC-5-SVCGWINVALIDEVE

SVC-4-SVCCALLTABLEINI

SVC-4-SAPISENDFAIL

SVC-4-SVCIRMUPDATEFAI

SVC-4-SVCIRMCBFAIL

SVC-4-SVCRECALLOCFAIL

SVC-4-SVCRECFREEFAILE

SVC-4-SVCVPIVCIFREEFA

SVC-4-SVCHASHTABLEDEL

SVC-7-CHECKSUMMISMATC

SVC-7-ATMSPIRESTARTRE

SVC-7-SAPIRESTARTIND

SVC-7-PXMSWITCHOVER

SVC-7-VXSMSWITCHOVER

SVC-4-TIMERCREATEFAIL

SVC-4-TIMERSTARTFAIL

SVC-4-TIMERSTOPFAIL

SVC-4-UNEXPECTEDSVCCA

SVC-4-HASHTABLECREATE

SVC-4-HASHTABLEDESTRO

SVC-4-HASHTABLEENTRYC

SVC-4-ITERATORINITFAI

SVC-5-CTCEVTUNKNOWN

SVC-5-SVCMSGPROCESSFA

SVC-5-RESYNCBACKOFF

DDTS: VBD

VBD-2-MOD_INIT_FAIL

VBD-5-RES_ALLOC_FAIL

VBD-5-RES_RELEASE_FAI

VBD-4-NULL_POINTER_ER

VBD-5-UNSUP_FEATURE

DDTS: VMATM

VMAT-2-NO_MEMORY

DDTS: vpro

VPRO-2-INIT_FAIL

VPRO-4-INVALID_IRM_OP

VPRO-4-EVENT_GENERR

VPRO-7-EVENT_GENINFO

VPRO-4-IRM_COMMIT_FAIL

DDTS: vsi

VSIS-7-VSIS_MSGQ

DDTS: pxm-connmgm

VRM-5-CONN_RSRV

VRM-5-CONN_CMT

DDTS: vxsm-apps

APS-6-ADD_LN

APS-6-DEL_LN

APS-6-CNF_SFBER

APS-6-CNF_SDBER

APS-6-CNF_WTR

APS-6-CNF_DIR

APS-6-CNF_REV

APS-6-CNF_PROTOCOL

APS-3-SF_DECL

APS-3-SF_DECL_CLEAR

APS-3-SF_BER_DECL

APS-3-SF_BER_DECL_CLE

APS-3-SD

APS-3-SD_CLEAR

APS-2-PSB_FAIL

APS-2-CHAN_MISMATCH

APS-4-PSBF_CLEARED

APS-4-CHAN_MIS_CLEARE

APS-2-FAR_END_FAIL

APS-4-FAR_END_FAIL_CL

APS-2-MODE_MISMATCH

APS-6-MODE_MIS_CLEAR

APS-3-SW_SF

APS-3-SW_SD

APS-3-SW_REV

APS-3-SW_RELEASE

APS-3-SW_LOCK

APS-3-SW_FORCE_WTOP

APS-3-SW_FORCE_PTOW

APS-3-SW_ANNXB_FORCE

APS-3-SW_MAN_WTOP

APS-3-SW_MAN_PTOW

APS-4-SW_CLEAR_FAIL

APS-4-SW_LOCK_FAIL

APS-4-SW_FORCE_WTOP_F

APS-4-SW_FORCE_PTOW_F

APS-4-SW_MAN_WTOP_FAI

APS-4-SW_MAN_PTOW_FAI

APS-4-SW_SF_FAIL

APS-4-SW_SD_FAIL

APS-6-SW_SERVICE

APS-6-PSB_INCONSISTEN

APS-6-PSB_INVALID_DET

APS-3-PRIMARY_SEC_MIS

APS-3-PRIMARY_SEC_SWA

APS-6-SWOVER_INFOLOG

DDTS: ssi

SYS-2-DCAPRECVTASKFAI

SYS-4-TMINITFAIL

SYS-2-DCAPTASKMONFAIL

SYS-2-DCAPRPCCBFAILED

DDTS: vxsm-line

LAM-4-INV_PTR

LAM-4-DSX1_INV_INDEX

LAM-4-DS3_INV_INDEX

LAM-4-OC3_INV_INDEX

LAM-4-STS1_INV_INDEX

LAM-4-TRAP_ERR

LAM-4-DSX1_GEN_ERR

LAM-4-DS3_GEN_ERR

LAM-4-OC3_GEN_ERR

LAM-4-GEN_ERR

LAM-7-GEN_INFO

LAM-4-DSX1_ALM_ON

LAM-4-DSX1_ALM_OFF

LAM-4-DS3_ALM_ON

LAM-4-DS3_ALM_OFF

LAM-4-OC3_ALM_ON

LAM-4-OC3_ALM_OFF

LAM-7-GEN_EVENT

DDTS: vxsm_mgcp

VXSM-4-VXSM_MGCP_GENER

VXSM-7-VXSM_MGCP_GENIN

DDTS: MTT

MTT-4-OUTOFTIMERS

MTT-4-TIMERUNINITIALI

MTT-4-INVALIDPARAM

MTT-4-TIMERALREADYCRE

DDTS: ssi

SYS-4-BCNOVRAMGETERRO

SYS-4-BCNOVRAMGETBADS

DDTS: DAT

PROG-7-DIRECTORY_CREAT

DDTS: VXSMSSIF

VXSM-5-UNSUPPORTED

VXSM-4-NoTmTable

VXSM-5-BADADDR

VXSM-5-HEAPCREAT

VXSM-5-PAKTYP

VXSM-4-BadTimer

VXSM-4-TickFailed

VXSM-5-DBLFREEERR

DDTS: vxsm_apps

STAT-4-ERROR

STAT-5-LOG

DDTS: vxsm-dd

T1E1-6-T1E1_BC_ERROR

DDTS: vxsm-dd

T1E1-6-T1E1_LIU_ERROR

DDTS: vxsm-line

TDM-6-INV_PTR

TDM-6-DSX1_INV_INDEX

TDM-6-DS3_INV_INDEX

TDM-6-OC3_INV_INDEX

TDM-6-STS1_INV_INDEX

TDM-6-RPC_ERR

TDM-6-DSX1_GEN_ERR

TDM-6-DS3_GEN_ERR

TDM-6-OC3_GEN_ERR

TDM-6-GEN_ERR

TDM-7-GEN_INFO

DDTS: TEMUX84

TMX-6-ERR

DDTS: vxsm-dd

TSI-6-INV_PTR

TSI-6-INV_Q_ID

TSI-6-INV_SEG_ID

TSI-6-INV_CONN_MODE

TSI-6-INV_STREAM

TSI-6-INV_CHAN

TSI-6-INV_DEV

TSI-6-INV_IDS

TSI-6-INV_LOG

TSI-6-Q_FULL

TSI-6-Q_EMPTY

TSI-6-END_PTS_NOT_CON

TSI-6-Q_MISMATCH

TSI-6-UNAVAL_END_PTS

TSI-6-NOT_MATCH_PTS

TSI-6-CH_NOT_IN_USE

TSI-6-ILLEGAL_CONN

TSI-6-GEN_ERR

TSI-7-GEN_INFO

DDTS: vxsm-dd

UMPR-6-UMPR_ERROR

DDTS: vsi

VSIS-7-VSIS_MSGQ

VSIS-7-INFO_STR

VSIS-7-VSI_IRM_INFO_ST

VSIS-7-VSI_IRM_ERROR

VSIS-7-VXSM_INFO_STR

VSIS-7-VXSM_INFO_STR_C

VSIS-7-VXSM_ERROR


Error Messages for MGX Release 5.0.00


New and Modified Error Messages for MGX Release 5

This chapter lists the error messages (also called Events) that were added or modified since MGX Release 4.0.10. For example:

MGX_4.0.10-5.0.0_logs_NEW : NEW means the message was added to MGX Release 5.

MGX_4.0.10-5.0.0_logs_MOD : MOD means the message was modified for MGX Release 5.


Note The latest release for the Service Expansion Shelf (SES) for the BPX switch is SES 4.0.15. That is, SES does note have a Release 5.


The messages have the same format used in earlier error message manuals, that is the DDTS component is followed by individual messages.

DDTS: snmp-ma

CB_S-5-PROXYERRORMISC

SEVERITY: Warning
FORMAT: %s(): %s
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: General Failure.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: "On PXM:
1. dspcds
2. dsplog
3. dsperr
4. dsprev

DDTS: config save restore

CUTW-5-STATIC_DEL_FAIL

SEVERITY: Warning
FORMAT: (Line %d:errno 0x%x)Static file deletion resulted in %s for slot %d on controller card %d
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Failed to remove static connection files from a controller card. There might be disk issues (refer errno)
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: snmp-ma

MIB-7-UNKNOWNFRONTMOD

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

DDTS: vsi

VSIC-5-VSICGENERR

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

DDTS: drivers

SAR-7-GEN_INFO

SEVERITY: Information
FORMAT: line: %d, %s, QE: %d, errno:0x%x, genCode:0x%x
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: Logging gen info
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: shm

SHM_-7-PXM_CBC_RDY

SEVERITY: Information
FORMAT: SHM INFO: Peer PXM cell bus card state is Ready for slot %d, Log Count: %d, Tick Value: %d
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: tMon detected peer pxm cell bus card state is Ready
RECOMMENDED ACTION: No action is required. The peer PXM card is detected in Cbc Ready State
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.

SHM_-7-PXM_CBC_NOT_RDY

SEVERITY: Information
FORMAT: SHM INFO: Peer PXM cell bus card state is Not Ready for slot %d, Log Count: %d, Tick Value: %d
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: tMon detected peer pxm cell bus card state Not Ready
RECOMMENDED ACTION: No action is required. The peer PXM card is detected in Cbc Not Ready State
EXPLANATION: An error has occurred while an operation was performed on an SHM SME Event Engine timer. the error type is specified in the event log string
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Enter the CLI commands dspcds, dspcd (for PXM and for the slot the error is found), dspver, dsperr, ls C:/FW before calling the Cisco Techincal support representative.

SHM_-5-SSM_EVT_DROP

SEVERITY: Warning
FORMAT: SHM SSM ERR: default case for [cur state: %s [%d] event: 0x%-4.4x]
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: The SHM SSM did not process the event while in this state
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: snmp-ma

SUBA-4-FAILED_RESOLVE_

SEVERITY: Error
FORMAT: %d: Could not resolve EPID %s. Error 0x%x.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: EPID resolve failed. Subagent will not be registered.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect output from dsplog, dsprev before notifying TAC.

DDTS: ssi

SRPR-5-INVALID_DBID

SEVERITY: Warning
FORMAT: %s(%s) for syncRam DBID 0x%x which might have been removed
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Synchronous Protocol Error: Input parameter ssiDbid is invalid
RECOMMENDED ACTION: Please capture the following information and call your Cisco technical support representative.
REQUIRED INFO: On PXM45:
1. dspversion
2. dsplog - collection the log over a period of two hours to cover what has happened before and after this error.
3. dsperr of the specified slot and specified error number.

SRPR-5-SR_IPCWARNING

SEVERITY: Warning
FORMAT: Cause [0x%x] in evaluate of DbId=%x [%s] for Tid=0x%x [%s].
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Synchronous Protocol Warning: Message is either not yet in the Rxmt queue or already removed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

SSI-5-ME_LOCKFAIL

SEVERITY: Warning
FORMAT: Attempt to lock resource %s for op %d has failed (current owner task 0x%x - %s).
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: An attempt to lock a resource has failed since it is currently locked by the specified owner task. This may be innocuous, e.g. the resource may already be locked by another task. Consult the event log for events leading up to this occurrence.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Take core dump. Collect event and error logs.

DDTS: AAA

AAA-5-NO_AUTH_FOUND

SEVERITY: Warning
FORMAT: No authorization found for user '%.16s'
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The user was authenticated but the switch could not authorize them for commands because of one of the following:
1. Authorization is configured for local and the user does not exist in the local database.
2. Authorization is configured for root and the user is not the root user cisco.
3. Authorization is configured for a remote ACS method with local as the fallback. The remote ACS is unreachable, so we fell back to the local method and the user does not exist in the local database.
4. Authorization is configured for a remote ACS method with root as the fallback. The remote ACS is unreachable, so we fell back to the root method, and the user is not the root user, cisco.
RECOMMENDED ACTION: Double check the configured authentication and authorization methods, and ensure that they are consistant with each other. Ensure that the user is correctly entered for both methods. This usually happens when the methods are mixed, such as TACACS+ authentication and local authorization (or the reverse) in which case the administartor has to manually ensure the local and remote databases are synchronized. Note that even if the user exists in both databases, their passwords must also match in the two databases otherwise one will fail. The best recommendation is to avoid mixing the methods, and use only local or only TACACS+ for both authentication and authorization.
REQUIRED INFO: No Required Info

AAA-4-INV_TRC_INDEX

SEVERITY: Error
FORMAT: nextIndex(%d) is invalid. Valid range is [%d..%d].
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: This error is logged when the TACACS+ trace internal data structure is corrupted. The index pointing to the next buffer entry is 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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - dspaaa-tac-trace detail (This command might not complete successfully because the trace buffer index is in error. - sh> aaaShowTacacsTrcCtl - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-CLI_RSP_ERR

SEVERITY: Error
FORMAT: %.23s failed with rc=%d cmdType expected=%d cmdType returned=%d cmdStatus=%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: The AAA CLI backend failed to complete the CLI request.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. 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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -mod SSI - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-INV_SVR_ID

SEVERITY: Error
FORMAT: Invalid server id %d. Valid range is [0..%d]
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: The server id is used to index into the server table and this id is 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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspaaa (Note: this command might not complete succesfully since the server linked list is corrupted.) - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-DEL_EMPTY_LIST

SEVERITY: Error
FORMAT: Server deletion error for server %d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Attempting to delete the specified server from an empty linked list.
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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspaaa (Note: this command might not complete succesfully since the server linked list is corrupted.) - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-INV_SVR_PTRS

SEVERITY: Error
FORMAT: Invalid server pointer(s). serverId:0x%x next:0x%x prev:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: The next and/or previous pointer for the specifified server in the linked list is 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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspaaa (Note: this command might not complete succesfully since the server linked list is corrupted.) - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-SVR_RBLD_ERR

SEVERITY: Error
FORMAT: Failed to rebuild server linked list. count:%d, max:%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Error detected while rebuilding the server linked list. The server database might be corrupted on the disk.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. 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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspaaa (Note: this command might not complete succesfully since the server linked list is corrupted.) - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-SHC_REGCOMP_ERR

SEVERITY: Error
FORMAT: Unable to compile the regular expression '%.40s'
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Error detected while compiling the regular expression. This regular expression is used to identify function names.
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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dsplog -mod CLF - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> shcLogFileCtlShow - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-SHC_BUF_ERR

SEVERITY: Error
FORMAT: Buffer to small for shellconn logging. bufsz:%d, need:%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Unable to format the output string. The output buffer provided is too small.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. 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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dsplog -mod CLF - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> shcLogFileCtlShow - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-7-SHC_LOG_TRUNC

SEVERITY: Information
FORMAT: Shellconn log entry is too long, %d, truncated to %d.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The shellconn log entry length is too long. It is truncated to fit into the shellconn logging a data buffer.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

AAA-7-SHC_USRNM_TRUNC

SEVERITY: Information
FORMAT: The username (%.40s) length is %d, truncated to %d chars
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The user name is too long. It is truncated to fit into the shellconn logging data buffer.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

AAA-7-SHC_CDTYP_TRUNC

SEVERITY: Information
FORMAT: The card type (%.40s) length is %d, truncated to %d chars
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The card type string is too long. It is truncated to fit in the shellconn logging data buffer.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

AAA-4-UNKN_SVR_TYPE

SEVERITY: Error
FORMAT: Unknown server type: %d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: The server type is 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: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspaaa (Note: this command might not complete succesfully since the server linked list is corrupted.) - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-7-TACACS_ADMN_MSG

SEVERITY: Information
FORMAT: ACS %.21s: %.101s
FLAG: No Flag
THROTTLING: 10 Minutes
EXPLANATION: The ACS has sent back an adminiatrative message in the authorization request.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

AAA-5-W_DEFAULT_PRIV

SEVERITY: Warning
FORMAT: No privilege level RX from ACS: %.21s. Using default level of '%.10s'
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The remote ACS did not provide a privilege level so the configured default privilege level specified was applied. If the default privilege level is NOUSER_GP, then the user will not be able to log on.
RECOMMENDED ACTION: You can use the configured default privilege level, or you can configure the ACS to supply the privilege level for the user.
REQUIRED INFO: No Required Info

AAA-7-TIMEOUT_CHANGED

SEVERITY: Information
FORMAT: Session timeout changed to %d seconds by ACS
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The remote ACS changed the session timeout value
RECOMMENDED ACTION: If you do not want the session timeout changed, then change the configuration of the ACS to not send a timeout change AVP with the authorization response message.
REQUIRED INFO: No Required Info

AAA-4-IE_FUNC_FAIL

SEVERITY: Error
FORMAT: %.40s failed. %.40s
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: A function call failed, as specified by the log.
RECOMMENDED ACTION: Each case is different, and therefore cannot give specific answer. However, if this problem persists and occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_FUNC_FAIL2

SEVERITY: Error
FORMAT: %.40s failed for %.40s 0x%x.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: A function call failed, as specified by the log.
RECOMMENDED ACTION: Each case is different, and therefore cannot give specific answer. However, if this problem persists and occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_FUNC_FAIL_E

SEVERITY: Error
FORMAT: %.40s failed. %.40s errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: A function call failed, as specified by the log.
RECOMMENDED ACTION: Each case is different, and therefore cannot give specific answer. However, if this problem persists and occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-UNEXPECTED_VAL

SEVERITY: Error
FORMAT: Unexpected %.40s 0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: The specified function received an unexpected value
RECOMMENDED ACTION: Each case is different, and therefore cannot give specific answer. However, if this occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-UNEXPECTED_VAL2

SEVERITY: Error
FORMAT: Unexpected %.40s 0x%x:%.40s
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: The specified function received an unexpected value
RECOMMENDED ACTION: Each case is different, and therefore cannot give specific answer. However, if this occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_UNEXP_START

SEVERITY: Error
FORMAT: Bad message state 0x%x:%.35s RX from message pointer 0x%x. Falling back.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: When attempting to start or continue a TACACS+ action, the tAAA task is sent a message telling it what to do. The first step is to initialize or find the context that is supporting this action. However, we could not do this because the incoming message had an incorrect state value. This error is logged, and then the authentication or authorization mechanism falls back to the next configured method.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_INVALID_PARM

SEVERITY: Error
FORMAT: Invalid parameter received: %.40s=0x%x.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The function logging this error has detected that the specified parameter has an invalid value.
RECOMMENDED ACTION: Each case is different, and therefore cannot give specific answer. However, if this occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-5-MISCNF_ENCRYPT1

SEVERITY: Warning
FORMAT: Message from ACS %d.%d.%d.%d/%d is encrypted, but we have no key configured.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Message exchanged via TACACS+ protocol are encrypted where both the server and the client are configured with the same secret key. We have detected that the incoming message from the server is encrypted, but we do not have a key configured. In short, this means that we cannot communicate with the TACACS+ server, and can lead to all sorts of inconviences such as delayed logins and command execution.
RECOMMENDED ACTION: 1. Configure the server's key on the MGX, making sure the values match between the server and the client (MGX) -OR-
2. Delete the key on the server (NOTE: deleting the servers key can cause problem with other MGX clients who HAVE their key configured, but now the server's key has been deleted. Moreover, this then means that the data, including passwords and login ids are transmitted in clear text, which is a security risk and is NOT recommended).
REQUIRED INFO: No Required Info

AAA-5-MISCNF_ENCRYPT2

SEVERITY: Warning
FORMAT: Message from ACS %d.%d.%d.%d/%d is unencrypted (cleartext) but we have a key configured.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Message exchanged via TACACS+ protocol are encrypted where both the server and the client are configured with the same secret key. We have detected that the incoming message from the server is NOT encrypted, i.e. clear text, a security risk, but the MGX DOES have a key configured. This configuration mismatch is NOT allowed. In short, this means that we cannot communicate with the TACACS+ server, and can lead to all sorts of inconviences such as delayed logins and command execution.
RECOMMENDED ACTION: 1. Configure the key on the server. (Note: if this server is managing other elements for TACACS+, which it probably is, this can lead to communication problems with the other managed elements because they probably do not have a key configured, and will therefore need to also have their key synchronized. This can lead to a lot of work but not having a key configured means data, including passwords and userids are transmitted in clear text -- a security risk)! -OR-
2. Delete the key on the MGX (Note: deleting the key on the MGX means that all data, including passwords and userids are transmitted in cleartext -- a secuirty risk!)
REQUIRED INFO: No Required Info

AAA-5-MISCNF_AVP_IDLE

SEVERITY: Warning
FORMAT: AVP value '%s' for %.10s is too large, cannot be larger than %d. RX from ACS %d.%d.%d.%d/%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The Attribute Value Pair received from the TACACS+ server was too large. If this AVP is an optional value it is ignored, if it is a required value then the authorization request fails, as per TACACS+ standards.
RECOMMENDED ACTION: Change the AVP value on the server to an acceptable value. The limit is specified by the warning message.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_AVP_PRIV

SEVERITY: Warning
FORMAT: AVP value '%s' for %.10s is invalid. RX from ACS %d.%d.%d.%d/%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The Attribute Value Pair received from the TACACS+ server was invalid. If this AVP is an optional value it is ignored, if it is a required value then the authorization request fails, as per TACACS+ standards.
RECOMMENDED ACTION: Change the AVP value on the server to an acceptable value. Valid values can be found in the configuration documentation or in the MGX's TACACS+ FSPEC (EDCS-263492)
REQUIRED INFO: No Required Info

AAA-5-MISCNF_AVP_VAL

SEVERITY: Warning
FORMAT: Integer value expected for AVP '%s', received '%s' from ACS %d.%d.%d.%d/%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The Attribute Value Pair received from the TACACS+ server was expected to be an integer but it contained a non-numeric value. If this AVP is an optional value it is ignored, if it is a required value then the authorization request fails, as per TACACS+ standards.
RECOMMENDED ACTION: Change the AVP value on the server to an acceptable value
REQUIRED INFO: No Required Info

AAA-5-MISCNF_AVP_SUPP

SEVERITY: Warning
FORMAT: Unsupported mandatory AVP from %d.%d.%d.%d/%d. AVP:'%.67s'
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The Attribute Value Pair received from the TACACS+ server was specified as a mandatory attribute. However, the attribute is either unsupported or unknown. By the TACACS+ standards, if the client (MGX) does not or cannot support a mandatory attribute, then the corresponding authorization action is considered a fail. Consequently, this user may not be able to log in or may not be able to execute the command that this authorization was for.
RECOMMENDED ACTION: Reconfigure the server to not send this AVP to the MGX.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_AVP

SEVERITY: Warning
FORMAT: Malformed AVP `%s'. Could not find '=' or '*'. RX from ACS %d.%d.%d.%d/%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The Attribute Value Pair received from the TACACS+ server did not comply with the TACACS+ standard for the AVP format. If this AVP is an optional value it is ignored, if it is a required value then the authorization request fails, as per TACACS+ standards.
RECOMMENDED ACTION: Change the AVP value on the server to an acceptable value
REQUIRED INFO: No Required Info

AAA-5-MISCNF_INVSTAT2

SEVERITY: Warning
FORMAT: Invalid status 0x%x RX from ACS %d.%d.%d.%d/%d. State 0x%x:%s expects 0x%0x or 0x%x.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The server sent us a status different from what the MGX expected. Consequently the MGX will treat this response as an errored response and fallback to the next configured server or method
RECOMMENDED ACTION: Reconfigure the server to return the appropriate status.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_INVPAP

SEVERITY: Warning
FORMAT: Invalid status 0x%x RX from ACS %d.%d.%d.%d/%d. State 0x%x:%s expects 0x%x or 0x%x.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The server sent us a status different from what the MGX expected for a FTP/SSH PAP login message. Consequently, the MGX will treat this response as an errored response and fallback to the next configured server or method.
RECOMMENDED ACTION: Reconfigure the server to return the appropriate status.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_INVSTAT3

SEVERITY: Warning
FORMAT: Invalid status 0x%0x RX from ACS %d.%d.%d.%d/%d. State 0x%x:%.35s expects 0x%0x, 0x%0x or 0x%x.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The server sent us a status different from what the MGX expected. Consequently, the MGX will treat this response as an errored response and fallback to the next configured server or method.
RECOMMENDED ACTION: Reconfigure the server to return the appropriate status.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_SVR_STAT

SEVERITY: Warning
FORMAT: ACS %d.%d.%d.%d/%d sent status 0x%0x, which is unsupported
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The server sent us an unsupported status type Consequently, the MGX will treat this response as an errored response and fallback to the next configured server or method.
RECOMMENDED ACTION: Reconfigure the server to return the appropriate status.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_RPM_TLNT

SEVERITY: Warning
FORMAT: Attempting telnet from RPM slot %d, that does not have exclusion enabled when TACACS+ command authorization is enabled.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: For command authorization, every command entered is sent to the TACACS+ server for validation. This causes problems for RPMs because they can do telnet, but you don't want to authorize the userid and password, and the various commands that the RPM is passing on to the telnet session. This is one reason, along with others that PXM's TACACS+ command authorization should not be enabled on RPMs. Instead the RPM should have their own TACACS+ command authorization configured. This warning is indicating that this misconfiguration has been detected.
RECOMMENDED ACTION: Don't use telnet from the RPM, or enable TACACS+ authorization on the RPM itself, and then exclude that RPM from the PXM's TACACS+ authorization.
REQUIRED INFO: No Required Info

AAA-5-SVR_MSG_ERROR

SEVERITY: Warning
FORMAT: ACS %d.%d.%d.%d/%d reported error status to %.16s's request, falling back.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The server sent back a status of error, indicating that it had encountered an error and terminated this session. The MGX will fallback to the next configured server or method.
RECOMMENDED ACTION: View the TACACS+ server's error logs to determine why it failed and correct the server as appropriate.
REQUIRED INFO: No Required Info

AAA-5-ACS_AUTHOR_PRIV

SEVERITY: Warning
FORMAT: ACS rejected authorization privilege level request for user '%.16s'.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The TACACS+ server has rejected the authorization privilege level request. This then means that the user will not be allowed to log in.
RECOMMENDED ACTION: View the TACACS+ server's error logs to determine why it failed, and correct the server appropriately
REQUIRED INFO: No Required Info

AAA-5-MISCNF_MSG_SIZE

SEVERITY: Warning
FORMAT: RX message size (%u) is larger than system maximum of (%u). Message type:0x%x from ACS %d.%d.%d.%d/%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The message received by the TACACS+ server was larger than the maximum message size supported by the system. The message is flushed, ignored, and this session will fall back to the next configured server or method.
RECOMMENDED ACTION: The server message is too big. The most probable cause is that too many Attribute Value Pairs were sent (although there may be others). Reconfigure the server to reduce the number of transmitted AVPs. The MGX doesn't support many, and so the server should not be sending more than is really needed. Use the 'dspaaa-stats detail' command to observe a listing of the AVPs supported by the MGX.
REQUIRED INFO: No Required Info

AAA-4-IE_SMALL_READ

SEVERITY: Error
FORMAT: We should have read %d bytes for socket 0x%x, but we read %d instead. Occurred for ACS %d.%d.%d.%d/%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We made a system call to read bytes from the socket, however, the number of bytes read was smaller than expected or calculated. The socket that this occurred on will be closed and the system will fall back to the next available server or method.
RECOMMENDED ACTION: This could be a coding error or a kernel problem. Monitor and report the number of occurrences.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_READ_FAIL

SEVERITY: Error
FORMAT: Socket read for socket 0x%x failed with errno:0x%x. Socket was servicing ACS %d.%d.%d.%d/%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We made a system call to read bytes from the socket, however the read failed.
RECOMMENDED ACTION: This could be a coding error or a kernel problem. Monitor and report the number of occurrences.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-5-MISCNF_SVR_FLSH

SEVERITY: Warning
FORMAT: Message received from ACS %d.%d.%d.%d/%d was flushed
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: A message received from the ACS server was flushed for some reason. Other event logs or errors will explain the reason.
RECOMMENDED ACTION: Examine the event log using dsplog -mod AAA for the specific log or error entries that immediately precede this one. They will give the details on why the message was flushed. This may be an internal coding problem, or it could be an ACS configuration issue. Refer to the recommended actions for the other log and/or error entries.
REQUIRED INFO: No Required Info

AAA-4-IE_AVP_NULL_PRM

SEVERITY: Error
FORMAT: Null parameter received: iCmpkey(0x%x), iThisKey(0x%x)
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The Attribute Value Pair hash lookup call back function was invoked with a NULL parameter. This means that one or more of the TACACS+ AVPs will not be processed, and quite possibly that the authorization message the AVP is for will simply fail. If iCmpKey is NULL then it implies that a NULL pointer was passed to the hash functionality and is a coding defect with the AVP's hash usage, if iThisKey is NULL then it implies that the hash infrastructure itself has a coding issue.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_AVP_TOOLONG

SEVERITY: Error
FORMAT: Key (%.75s) is larger than TACACS+ limit of %d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When the Attribute Value Pair hash table was populated, we discovered that the AVP's name, the key, was larger than the TACACS+ limit for a key. This AVP will still be added to the hash table, but it won't work because it is impossibly long so no TACACS+ message will ever match on it
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_AVP_HASH_ADD

SEVERITY: Error
FORMAT: Failed to add hash entry for AVP (%.40s)
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When the Attribute Value Pair hash table was populated, we could not add a hash entry for the AVP listed. Other entries in the event log should explain why the hash table insertion failed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_AVP_ZERO_LEN

SEVERITY: Error
FORMAT: Received AVP of size 0 from ACS %d.%d.%d.%d/%d. avplen:%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When the Attribute Value Pair processing function was invoked it was invoked with a zero length, which should not happen
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_AVP_NO_UNKN

SEVERITY: Error
FORMAT: Could not find 'unknown' AVP hash entry.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We received an AVP value that is not supported. Moreover, it is not even within our configured listing of UNSUPPORTED AVPs. So we attempted to pass it to our 'unknown' AVP processing routine. However, we could not find our 'unknown' entry in the hash table. If this AVP is an optional value it is ignored, if it is a required value then the authorization request fails, as per TACACS+ standards.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_TOO_BIG

SEVERITY: Error
FORMAT: Connection index %d is too big, should be less than %d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The specified routine did a sanity check on the socket connection index parameter and determined that it was too large. It is very probable that this failure will cause other AAA related errors. Worst case this will cause the current TACACS+ AAA action to stall, meaning the login or command execution process will stall until the CLI declares the AAA task as unresponsive at which point the CLI will fall back to the classic (or root, cisco) authentication or authorization mechanism.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_CLOSE_TO

SEVERITY: Error
FORMAT: Could not cancel the connection close timeout for connection 0x%x. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When we attempt to reuse a connection that is pending closure, we try to cancel the timeout that triggers the closure. However, in this instance we could not cancel the timeout, there was some problem with the timeout infrastructure. While this should not occur, the module is designed such that when the timeout does go off and we try to close the connection, we will first check if it is in use (which it is, that's why we are cancling the timeout). In which case the connection is NOT closed, and another error is logged, complaining that the connection close timeout went off for a connection that is still in use. The errno associated with the error should give the reason or clue as to why the timeout functionality failed. During unit testing it was found that this sort of problem could occur if task1 created the timeout, but then task2 tried to cancel the timeout (i.e. tAAA created timeout and tAAAsub tried to cancel).
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_UNAVAIL

SEVERITY: Error
FORMAT: No TPLUS TCP connections available
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When we attempt to obtain a connection to a server for a TACACS+ AAA action but we could not get a connection entry. Meaning that we have a resource leak for the TACACS+ connections. The protocol will fall back to the classic or root (cisco) AAA methods.
RECOMMENDED ACTION: If a redundant PXM, you can try a double switch over. If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information, BEFORE applying the recommened action work around: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_COUNT

SEVERITY: Error
FORMAT: Usage count %d for connection %d is too high, should be less than %d. Correcting to newly calculated value of %d.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When obtaining or freeing a server connection for a TACACS+ AAA action, the code observed that the usage count for the connection was too high, so it fixed it.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_START_TO

SEVERITY: Error
FORMAT: Could not schedule connection close timeout for connection 0x%x. errno:0x%x. Closing immediately instead.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When the last TACACS+ context is done with a server connection that supports multiplexing, we set a linger timer to have it stay awake for a bit before finally close it. This way future TACACS+ sessions can use the already allocated resource. However, in this case, we could not set the linger timeout, so we log this error and close it immediately. The errno associated with the error should give the reason or clue as to why the timeout functionality failed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_CLOSE

SEVERITY: Error
FORMAT: Attempting to close connection %d that is still in use. Canceling close
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The server connection linger timeout went off, and before closing we validate that it really should be closed. In this case we found that the server connection really was in use, so we canceled the server connection close action. This is most likely a side effect of a IE_CON_CLOSE_TO, but it could also be a coding defect.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_COUNT2

SEVERITY: Error
FORMAT: Usage count %d for connection %d is incorrect, should 0. Correcting.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The server connection linger timeout went off, and before closing we validate that it really should be closed. In this case we found that the server connection usage count was non-zero, when it really should be zero! So, we corrected the usage count and closed the server connection
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_RTRY_TO2

SEVERITY: Error
FORMAT: Could not schedule connection retry timeout for connection 0x%x. errno:0x%x. Falling back.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The server connection is opened as a non-blocking socket. It is quite possible that when we get to the send the socket has not been completely openend, which we gracefully detect and set a transmit retry timeout. In this case, we could not set the transmit retry timeout. So we call the fall back functionality which will attempt this TACACS+ AAA action with the next available server. The errno associated with the error should give the reason or clue as to why the timeout functionality failed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_RTRY_TO

SEVERITY: Error
FORMAT: Could not cancel the connection retry timeout for connection 0x%x. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When attempting to cancel the connection retry timeout but the action failed. Timeout cancelation can fail if:
1. an invalid call back function pointer is specified
2. The timeout was canceled but the timeout functionality could not restart the timer for the next TO in the queue.
3. The TO was not set.
4. The TO was set by task1, but task2 is attempting to clear the timeout. Errors are logged by the timeout functionality for each of these cases. The errno associated with the error should give the reason or clue as to why the timeout functionality failed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_RCV_LIST

SEVERITY: Error
FORMAT: Connection linked list did not terminate when expected. count (%d), i_conn (%d)
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The routine that monitors the incoming TACACS+ server connections determined that the list of open connections is impossibly large, so it corrected it self by existing as soon as the maximum possible connection limit was reached.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_CHECK_TO

SEVERITY: Error
FORMAT: Could not schedule connection check timeout. errno:0x%x. Falling back.
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: We were not able to start the timeout that triggers the receival of data on TACACS+ server connections. Consequently all TACACS+ functionality will not work, causing timeouts that eventually fall back to the classic or root (cisco) authentication and authorization methods. The errno associated with the error should give the reason or clue as to why the timeout functionality failed.
RECOMMENDED ACTION: If a redundant PXM, you can try a double switch over. If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_READ_BIG

SEVERITY: Error
FORMAT: Read too many bytes, %d, should have stopped at %d. Occurred for ACS %d.%d.%d.%d/%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When reading bytes from a server connection, we detected that we read too many. The server connection will be shut down, and all TACACS+ contexts using that connection will fall back to the next configured server.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_ABORTSTR

SEVERITY: Error
FORMAT: TACACS+ server abort string was not set
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We encountered an error with the servers message and needed to tell the server to abort the current action. However, the optional abort string explaining why was not set. Consequently, the MGX has terminated the current AA action, falling back to the next server or method, but no abort string was sent to the server.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_FLUSH_SZ

SEVERITY: Error
FORMAT: Flushed too many bytes, %d, should have stopped at %d. Occurred for ACS %d.%d.%d.%d/%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We were flushing a message, but we detected that we flushed too many bytes. The server connection will be shut down, and all TACACS+ contexts using that connection will fall back to the next configured server.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_PERSISTS

SEVERITY: Error
FORMAT: Connection to ACS %d.%d.%d.%d/%d still open. Closing Now.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The sanity routine was invoked to validate that all connections to a server were closed. However, we found that a connection was still open to it. It is now closed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_NO_ROOT

SEVERITY: Error
FORMAT: Mandatory %.15s method, root (cisco), not found. Adding now.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Sanity checks have found that the CLI's or FTP's authentication or authorization method list does not contain the mandatory method for root (cisco) authentication or authorization. This error is logged, and the method is added.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_EMPTY

SEVERITY: Error
FORMAT: No %.15s methods detected. Initializing to defaults
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Sanity checks have found that the CLI's or FTP's authentication or authorization method list is not initialized. This error is logged and then it is initialized to the default of root (cisco) authentication or authorization
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_BAD_RSP

SEVERITY: Error
FORMAT: Unexpected %.15s method response value 0x%x:%.40s
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The routine recevied an unexpected response value to its authentication or authorization request. The authentication or authorization request is therefore failed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_UNKN_P

SEVERITY: Error
FORMAT: Unknown %.15s method function pointer %p
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The routine that translates the address of a method function into its corresponding string has been called with an invalid method address. The string 'Unknown' is returned.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_UNKN_P2

SEVERITY: Error
FORMAT: Unknown %.15s method function pointer %p. Removing.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The sanity routine has detected an invalid function pointer in its method list and is removing it.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_UNKN

SEVERITY: Error
FORMAT: Unknown %.15s method 0x%x specified
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not determine the authentication method used because the paramater value is unexpected. Hence the authentication method sent in the AUTHORIZATION message being generated is set to `NOT SET'
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_STAT

SEVERITY: Error
FORMAT: Invalid method 0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The method parameter for the AAA stat update routine is an invalid value. Consequently stats will not be updated appropriately.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_CISCO

SEVERITY: Error
FORMAT: Unexpected method 0x%x. Applying root (cisco) %.15s method
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The local authentication or authorization mechanism was invoked with an invalid method type which distinguishes between local or root authentication. Since we do not know what the method should be and we do not want to lock out the CLI completely we apply the strictist method, root (cisco)
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CCMODE_UNKN

SEVERITY: Error
FORMAT: Unexpected value for aaa_sm_cc_mode:0x%x. Cleaning up.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: aaa_sm_cc_mode was found to be an invalid value, it is being changed back to its default. This could mean that shellconn authorization exclusion, or logging might have HAD some issues, but the cleanup has resolve the problem.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CTX_TOO_BIG

SEVERITY: Error
FORMAT: TACACS+ context index %d is to big, should be less than %d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The specified routine did a sanity check on the TACACS+ context index parameter and determined that it was too large. It is very probable that this failure will cause other AAA related errors. Worst case this will cause the current TACACS+ AAA action to stall, meaning the login or command execution process will stall until the CLI declares the AAA task as unresponsive at which point the CLI will fall back to the classic (or root, cisco) authentication or authorization mechanism.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_TASK_STATE

SEVERITY: Error
FORMAT: tAAA failed to complete transition for %.40s
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: The task was unable to complete the specified state transition because the corresponding ctc<state>Confirm() function call failed.
RECOMMENDED ACTION: Each case is different, we cannot give specific resolutions. However, if this occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby, or to reset the active.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_TASK_VALUE

SEVERITY: Error
FORMAT: Unexpected %.40s 0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: The specified function received an unexpected value
RECOMMENDED ACTION: Each case is different, we cannot give specific resolutions. However, if this occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby, or to reset the active.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_TASK_VALUE2

SEVERITY: Error
FORMAT: Unexpected %.40s 0x%x:%.29s
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: The specified function received an unexpected value
RECOMMENDED ACTION: Each case is different, we cannot give specific resolutions. However, if this occurred on the standby a possible work around would be to reset the standby. If this occurred on the active a possible work around is to do a switch over to the standby, or to reset the active.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SHCL_FAIL_I

SEVERITY: Error
FORMAT: Could not initialize shellconn logging. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Shellconn logging could not be initialized during tAAA initialization. However, it is not a critical component of AAA so tAAA will still come up. However, shellconn commands will not be logged.
RECOMMENDED ACTION: If a redundant PXM, you can try a double switch over. If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_TASK_FAIL_A

SEVERITY: Error
FORMAT: Task cannot go active. %.100s
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: Some error was encountered while the tAAA task was trying to transition to the active ready state. Consequently only the default authentication and authorization method of root (cisco) will work. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over. If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_TASK_FAIL_S

SEVERITY: Error
FORMAT: Task cannot go standby. %.100s
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: Some error was encountered while the tAAA task was trying to transition to the standby ready state. Consequently only the default authentication and authorization method of root (cisco) will work. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: Reset the standby PXM
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_ALLOC

SEVERITY: Error
FORMAT: Cannot allocate IPC buffer. Request type:0x%x:%.25s, size:%d, errno:0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not allocate a message buffer for exchanging information among the tasks. Consequently the current AAA action will stall until the CLI declares tAAA unresponsive and falls back to the next configured authentication or authorization method. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_ALLOC2

SEVERITY: Error
FORMAT: Cannot allocate IPC buffer. Request type:0x%x, subtype:0x%x:%.32s, size:%d, errno0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not allocate a message buffer for exchanging information among the tasks. Consequently the current AAA action will stall until the CLI declares tAAA unresponsive and falls back to the next configured authentication or authorization method. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_SEND

SEVERITY: Error
FORMAT: IPC send failure for type:0x%x:%.32s, errno:0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not send send messages among the tasks. Consequently the current AAA action will stall until the CLI declares tAAA unresponsive and falls back to the next configured authentication or authorization method. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_SEND2

SEVERITY: Error
FORMAT: IPC send failure for type:0x%x, subtype:0x%x:%.32s, errno:0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not send send messages among the tasks. Consequently the current AAA action will stall until the CLI declares tAAA unresponsive and falls back to the next configured authentication or authorization method. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_TO

SEVERITY: Error
FORMAT: Could not schedule timeout request type:0x%x:%.32s. errno:0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not set the response timeout for the specified message type that is to be sent to the subtask. If the messages are responded to this will have no impact. If the messages are not responded to, we will never detect when they should have timed out and the initialiation action will stall. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_BIND

SEVERITY: Error
FORMAT: Could not bind the tAAA EPID, %.40s. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When the card goes acitve tAAA binds its EPID. In this case the bind failed. Consequently AAA functionality will not work, and only root (cisco) authentication and authorization will be allowed. The errno associated with the error should give the reason or clue as to why the timeout functionality failed. Also refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redudnant PXM, switch over. If a single PXM, reset the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_EPIDFIND

SEVERITY: Error
FORMAT: Could not find tAAA's epid, for name:%.40s, slot:%d, errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: tAAA's EPID could not be found when it should be created, initialized and bound already. The errno associated with the error should give the reason or clue as to why the timeout functionality failed. Also refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redudnant PXM, switch over. If a single PXM, reset the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_INIT

SEVERITY: Error
FORMAT: Could not %.10s tAAA Epid, errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: tAAA's EPIDs are created and initialized when the task initializes. One of these steps failed. The errno associated with the error should give the reason or clue as to why the timeout functionality failed. Also refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redudnant PXM, switch over. If a single PXM, reset the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_RSP_SIZE

SEVERITY: Error
FORMAT: Bad response RX. Size is zero. Wait state of type 0x%x, subtype 0x%x:%.35s
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The response received from tAAA was invalid. The response is expected to have data, but this one did not. Consequently this will return an error to the AAA functinality, causing it to fall back to the next configured method.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_IPC_RSP_BAD

SEVERITY: Error
FORMAT: RX Message type 0x%x was unexpected, waiting for a 0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The response received from tAAA was not of the expceted type. Consequently, this will return an error to the AAA functionality, causing it to fall back to the next configured method.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_STASK_SPAWN

SEVERITY: Error
FORMAT: Subtask initialization failed. %.40s. errno:0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: Some error was encountered while attempting to spawn and initialize the AAA subtask, tAAAsub. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_STASK_FAIL_I

SEVERITY: Error
FORMAT: tAAA sub task initialization failed. %.30s. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Some error was encountered while trying to initalize the AAA sub task. Consequently only the default authentication and authorization method of root (cisco) will work. Refer to other event and error logs as well as the supplied errno to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a double switch over. If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_STASK_TO

SEVERITY: Error
FORMAT: Could not schedule WDT for subtask response. errno:0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not set the response timeout for the subtask's initialization. If the subtask comes up this will have no impact, but if it doesn't then the AAA initialization sequence will stall. Refer to other event and error logs to determine the exact failure.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_STASK_RSP

SEVERITY: Error
FORMAT: Invalid response RX from subtask. Type:0x%x, Response:0x%x:%.32s
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: We received an unexpected response from the subtask. The response will be ignored.
RECOMMENDED ACTION: This should not be too much of an issue. Refer to other AAA events, using the 'dsplog -mod AAA' command to determine if there are other AAA failures that might have been caused by this issue.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_STASK_BADRSP

SEVERITY: Error
FORMAT: RX %.30s, message type 0x%x:%.25s while in unexpected state 0x%x:%.30s
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: tAAA received a subtask response, but it was received in the wrong order. Consequently, the AAA task tAAA will not come up correctly, and authentication and authorization will be limited to the cisco method only.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_STASK_RSP_TO

SEVERITY: Error
FORMAT: tAAA did not RX subtask's %.40s
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: tAAA was waiting for a response from the subtask tAAAsub, but it never came. Consequently, the AAA task tAAA will not come up correctly, and authentication and authorization will be limited to the cisco method only.
RECOMMENDED ACTION: If a redundant PXM, you can try a switch over If a single PXM, you can try reseting the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_TPLUS_SIZE

SEVERITY: Error
FORMAT: Data structure size mismatch between %.30s(%d) and %.30s(%d).
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: A sanity check run at tAAA initialiation has detected a size mismatch between some cruicial AAA atastructures which can lead to protocol failures because of byte mismatches, or can cause incorrect disk saves or standby updates (ram syncs). Realisitically this error should never be seen in a customer image. This is a low level sanity check to weed out problems such as this during early test phases. This is most likely caused by a change to one of the datastructures but not to its corresponding structure, or caused by unexpected hidden spares caused by word or long alignment.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_PRIV_MISSING

SEVERITY: Error
FORMAT: tAAA did not return a privilege level for user %.16s
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: During a TACACS+ authorization request, the CLI asked tAAA for the user's privilege level, but it was not returned. The end result is that the user's authorization request errors and AAA falls back to the next configured method.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_USERNAME

SEVERITY: Error
FORMAT: Username '%.40s' is %d long, cannot exceed %d. Truncating
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The supplied username is too long. It is being truncated to system maximum.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_PASSWORD

SEVERITY: Error
FORMAT: Password is %d long, cannot exceed %d. Truncating
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The supplied password is too long. It is being truncated to system maximum.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CMD_LEN

SEVERITY: Error
FORMAT: Command '%.29s...' is longer than maximum length, %d, allowed by TACACS+ protocol. Truncating.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The supplied command strintg is too long. It is being truncated to the TACACS+ maximum.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_METH_ALLFAIL

SEVERITY: Error
FORMAT: All %.15s methods errored
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: All authentication or authorization methods errored. Realistically this should not happen in a customer image since the local and root (cisco) methods never return execution errors and they are always included in the method list. However, this sanity check is included for absolute robustness and for catching problems that might be intruduced during future developement.
RECOMMENDED ACTION: If a redundant PXM, switch over. If a single PXM, reset the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_AUTHOR_REQ

SEVERITY: Error
FORMAT: Invalid req_type parameter specified 0x%x:%.35s. Expected 0x%x or 0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The routine received an invalid parameter. Sanity checks have detected the invalid parameter, logged this error and will cause the TACACS+ action to error and fall back to the next configured method.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_AUTHEN_BUFF

SEVERITY: Error
FORMAT: Buffer is too small. Buffer size:%d, need:%d. Canceling action
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The authentication process failed because the code attempted to send a message with a buffer size that was too small. Authentication will fall back to the next configured method, local or root (cisco).
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CLI_INIT

SEVERITY: Error
FORMAT: Could not get AAA configuration.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The session could not obtain the AAA configuration, so it does not know which methods should be applied. Consequently the methods are left set at NONE. However, when we go to use the methods, we will detect that no methods are set and will log another error as we robustly initialize the methods to the most strict loging of root (cisco).
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_EXCPTN_STR

SEVERITY: Error
FORMAT: Could not find 'session' in the exception string '%.75s'
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The routine was invoked with an invalid exception string. We expect the excpetion string to contain 'session'. Realisitically this will not occur in a customer image as this check is a sanity check for hard coded strings and is used to detect coding errors during developement.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SVR_IDX

SEVERITY: Error
FORMAT: Server index %d is too large, must be less than %d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The servier index passed is too large, and is being ignored. This is a generic sanity check, and as such specific actions cannot be recommended. However, it is probable that other AAA events are logged for the failure as well and will help with guideance on how to react
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_RSYNC_DONE

SEVERITY: Error
FORMAT: SR_EVENT_SYNCDONE RX in unexpected state. State:0x%x:%.30s
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The event that indicates that the active is done syncing with us was recieved while in an unexpected state. Consequently the standby's RAM is most likely NOT sync'd to the active's.
RECOMMENDED ACTION: Reset the standby PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SRAPI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_RSYNC_SIZE

SEVERITY: Error
FORMAT: Data length %d larger than maximum %d for type 0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The size of the data that is to send to the standby is larger than the ramsync buffer size. Realistically this will never be observed in a customer image. This is a sanity check to quickly catch issues introduced during developement.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-5-MISCNF_SVR_MSG

SEVERITY: Warning
FORMAT: Invalid response value from ACS %d.%d.%d.%d/%d for %.40s, 0x%x. Should be 0x%x
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Sanity checks have shown that the value received from the server is invalid, as specified by the specifics of the event warning.
RECOMMENDED ACTION: It is possible that this is caused by the server and the MGX having different encryption keys, check that they are the same. If they are the same then debug the server to determine why it sent an invalid message and correct the server.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_SVR_MSG2

SEVERITY: Warning
FORMAT: Response from ACS %d.%d.%d.%d/%d only had a header.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Sanity checks have shown that message received from the server consisted only of a header and no data
RECOMMENDED ACTION: The server sent the MGX a message that had no data it only had the packet header. Debug the server to determine why it sent an invalid message and correct the server.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_AUTH_AVP

SEVERITY: Warning
FORMAT: ACS %.21s tried to change privilege level from CISCO_GP to %.10s. Change ignored.
FLAG: No Flag
THROTTLING: One Hour
EXPLANATION: Sanity checks have shown that the MGX is configured for TACACS+ command authorization, but the last authorization message contained a priv-lvl attribute value pair that is attempting to change the user's privilege level from CISCO_GP to some other value. This would cause the authorization mechanism on the MGX to break, since the local authorization mechanisms are still done, even though TACACS+ command authorization is also done. In order to provide the required functionality, the privilege level is set to CISCO_GP, so all local checks pass, thereby leaving the ultiamte authorization decision up to the TACACS+ server. The privilege level change in the authorization request is ignored.
RECOMMENDED ACTION: Reconfigure the TACACS+ server so that it does not send a priv-lvl AVP to this MGX.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_CSCO_AVP

SEVERITY: Warning
FORMAT: ACS %.21s has changed 'cisco' users privilege level to %.10s.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Sanity checks have shown that the MGX is configured for TACACS+ group authorization, and the cisco users privilege level is being set to a value other than CISCO_GP. While this is an allowed configuration, it is not a recommended configuration, as it can make debugging by cisco personnel more difficult.
RECOMMENDED ACTION: Reconfigure the TACACS+ server so that it sets the cisco users privilege level to CISCO_GP.
REQUIRED INFO: No Required Info

AAA-5-MISCNF_CHALLENG

SEVERITY: Warning
FORMAT: ACS %d.%d.%d.%d/%d has sent a challenge for a %.4s login.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The MGX has been configured to do FTP and SSH authentication using the TACACS+ ASCII login message. TACACS+ ASCII logins support challenges. However, FTP and SSH do not support challenges, they provide username and password and expect back pass or fail. Sanity checks have found that the server is responding with a challenge. This will cause the a fallback to the next configured server or method.
RECOMMENDED ACTION: There are two options for fixing this issue:
1. Reconfigure the MGX so that is uses the TACACS+ PAP messaging for FTP and SSH authentication (assuming the TACACS+ server supports that message type).
2. Reconfigure the TACACS+ server so that it does not send challenges.
REQUIRED INFO: No Required Info

AAA-4-IE_CTX_P_BAD

SEVERITY: Error
FORMAT: Invalid AAA context pointer %p
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Sanity checks have shown that the TACACS+ context pointer is invalid.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CON_P_BAD

SEVERITY: Error
FORMAT: Invalid AAA connection pointer %p
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Sanity checks have shown that the TACACS+ connection pointer is invalid.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CTX_NOT_FREE

SEVERITY: Error
FORMAT: Attempting to do NEW initialization on a context that is not free. Canceling action
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Sanity check to make sure that when we allocate a context we initialize it correctly as NEW or REUSE, depending upon its initialization needs. In this case we attempted to do a NEW initialization on a context that was currently in use. We detect this and cancel the action. The end result is that we will fall back to the next configured server, and look for another context.
RECOMMENDED ACTION: If this problem occurs frequently, consider applying the following workarounds: -if a redundant PXM do a PXM switchover -if a non-redundant PXM, reset the active PXM.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CTX_DELETED

SEVERITY: Error
FORMAT: Context for Session Id %u has been deleted
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The context for the specifed session id has been deleted. The current authentication or authorization action will fall back to the next configured server or method.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CTX_UNAVAIL

SEVERITY: Error
FORMAT: Ran out of TPLUS contexts
FLAG: Stack Trace
THROTTLING: Ten minutes
EXPLANATION: Internal Error: We have run out of TPLUS contexts, therefore the current authentication or authorization action will fall back to the next server or method as appropriate.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod CLI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CTX_MISSING

SEVERITY: Error
FORMAT: Cannot find context for session id %u
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The message processing routine was invoked, and prior to the invocation the context exists, but somehow, magically, upon calling this routine the context disappeared. Realistically this cannot happen because the calling routine already validated that the context exists, however, this check is placed in the sub-routine for robustness.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CTX_CLOSE_TO

SEVERITY: Error
FORMAT: Could not cancel the context timeout for context 0x%x. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When attempting to cancel the context timeout but the action failed. Timeout cancelation can fail if:
1. an invalid call back function pointer is specified
2. The timeout was canceled but the timeout functionality could not restart the timer for the next TO in the queue.
3. The TO was not set.
4. The TO was set by task1, but task2 is attempting to clear the timeout. Errors are logged by the timeout functionality for each of these cases. The errno associated with the error should give the reason or clue as to why the timeout functionality failed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CTX_START_TO

SEVERITY: Error
FORMAT: Unable to schedule context timeout for context 0x%x. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We were unable to start the context timeout. If the server responds, then this will not be noticed, if the server does not respond, then the CLI will eventually declare tAAA unresponsive and fall back to the next configured method -- which could take 90 seconds orlonger. The errno associated with the error should give the reason as to why the timeout functionality failed.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_CTX_TO

SEVERITY: Error
FORMAT: Context timeout fired for context 0x%x, but the timeout flag is clear.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: As a sanity check, when the context timeout expires we double check that the flag that indicatse the timeout is pending, is set. If it is not set then we should not have the timeout firing so there is some sort of internal error. The code will then disregard, the context timeout, and rely on the CLI's IPC timeout, 90 seconds, to recognize that the AAA task isn't responding. This will then cause the authentication or authorization action to fall back to the next configured method.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SOCKET_FLUSH

SEVERITY: Error
FORMAT: Unrecoverable socket error for SesnId %u on ACS %d.%d.%d.%d/%d. All TACACS+ users of socket falling back.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Some low level internal socket error occurred causing an unrecoverable problem for the socket. All TACACS+ users of that socket will fallback to the next server or method. Refer to other event logs for further informations.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-5-W_SOCKET_FLUSH

SEVERITY: Warning
FORMAT: Bad msg for SesnId %u on ACS %d.%d.%d.%d/%d. Closing socket. All TACACS+ users of socket falling back.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: TACACS+ Server Error: A sanity check on the incoming TACACS+ message from the specified server failed. Moreover, this failure was such that the MGX decided that the current socket was unrecoverable. All TACACS+ users of the unrecoverable socket will fallback to the next server or method, and the socket is closed. Refer to other AAA event logs for further information.
RECOMMENDED ACTION: This issue might be caused by a mismatch of the server and MGX's encryption keys, validate that they are the same. If they are the same, then analyze the other AAA event log messages observed from the 'dsplog -mod AAA 'command as well as the server's error logs and then reconfigure the server appropriately.
REQUIRED INFO: No Required Info

AAA-4-IE_ENCRYPT_ERR1

SEVERITY: Error
FORMAT: Message for ACS %d.%d.%d.%d/%d is already encrypted, %.40s.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When encrypting the message to be sent to the server we observed that the buffer is already encrypted. The message exchange with the server is aborted, causing this authentication or authorization action to fall back to the next configured server or methd.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_BUFF_ALLOC

SEVERITY: Error
FORMAT: Could not allocate memory for TX/RX buffer. Size needed is %d. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We were unable to allocate a transmit and receive buffer for the TACACS+ authentication or authorization action. Consequently, this action will error, and we will fall back and try the next configure server or method, as appropriate.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod FIPC - dsplog -mod IPC - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SVR_WKUP_TO4

SEVERITY: Error
FORMAT: Cannot cancel wakeup time for server %d.%d.%d.%d/%d. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We couldn't delete the servers wakeup timer. Consequently the wake up timer will go off, even after the server has been deleted. This will then result in a IE_SVR_WKUP_TO1 being logged when the wake up code robustly checks and detects that the server to wake up does not exist. Refer to other event logs, errors and the erno for an reaspons why the timout functionality failed. During unit testing it was found that this sort of problem could occur if task1 created the timeout, but then task2 tried to cancel the timeout (i.e. tAAA created timeout and tAAAsub tried to cancel).
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SVR_WKUP_TO3

SEVERITY: Error
FORMAT: Unable to schedule deadtime timeout for server %d.%d.%d.%d/%d. errno:0x%d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not set the server's wakeup timer. Consequently the server will not be marked as dead and we will continue to try and communicate with it. If this occurs, this could lead to undesireable delays for authentication (logging on) or authorization (command execution). Refer to other event logs, errors and the erno for an reaspons why the timout functionality failed.
RECOMMENDED ACTION: A work around for this would be immediately correct the server so that it becomes responsive so the MGX does not have to mark it as dead. Another alternative is to remove the server from the server list, replacing it with a server that is response.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SVR_WKUP_TO2

SEVERITY: Error
FORMAT: Cannot cancel and then reschedule deadtime for server %d.%d.%d.%d/%d. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We could not delete the server's deadtime wake up timer in order for it to be rescheduled. The end result is that the server will wake up earlier than we originally wanted, which simply means we are not giving the server as much time as we would like to restart. Refer to other event logs, errors and the erno for an reaspons why the timout functionality failed.
RECOMMENDED ACTION: Contact the TAC to have a low priority defect opened for this case. The code as robustly detected this inconsistancy and responed accordingly, but it still should not be happening.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SVR_WKUP_TO1

SEVERITY: Error
FORMAT: Server was deleted, but wakeup timer was left set
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The server wake up timer went off but we could not find the server, which implies that it was deleted and the wake up timer was not stopped.
RECOMMENDED ACTION: Contact the TAC to have a low priority defect opened for this case. The code as robustly detected this inconsistancy and responed accordingly, but it still should not be happening.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod SSI - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SVR_DEL_TAG

SEVERITY: Error
FORMAT: Server delete issue, invalid server index 0x%x for server tag 0x%x.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: We where attempting to delete a server and the code responsible for ensuring that no AAA actions are currently using the server could not find the specified server to delete. Consequently we may have a situation where we attempt to move forward communicating with a server that no longer exists. Ultimately this may result in othe AAA related errors.
RECOMMENDED ACTION: Apply the appropriate workaround as specified below, if this occurred on: - the standby PXM, reset it. - the active PXM of a redundant PXM configuration, then do a switch over. - the active PXM of a single PXM configuration, then reset it.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_RANDOM_NUM

SEVERITY: Error
FORMAT: Random number generator failed to find unique random number after %d attempts. Forcing a unique number.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The random number generator failed to obtain a unique session id. So we forced it to be unique.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_MSG_CREATE_P

SEVERITY: Error
FORMAT: Bad message creation function pointer 0x%x, context:0x%x, state 0x%x:%.35s. Falling back.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The TACACS+ message creation pointer was not initialized when the AAA context was obtained. Sanity checks have found this and will cause a server or method fallback as appropriate.
RECOMMENDED ACTION: Report this issue to TAC so a defect can be created to resolve it.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_NULL_STAT_P

SEVERITY: Error
FORMAT: NULL Stat update pointer for %.20s, field %.20s, stattype 0x%x.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When updating stats, we do a sanity check to make sure the stat pointer was calculated correctly. In this case it was not. So the statistic will not be updated correctly.
RECOMMENDED ACTION: Report this to the TAC as a low priority defect to resolve. This will not cause any system problems as the code has detected the problem and robustly accounted for it.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_ABORT_MSG_SZ

SEVERITY: Error
FORMAT: Abort message is %d long, longer than limit of %d. Truncating.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: If the ACS does something that the MGX does not like, the MGX will send the ACS an abort string to cancel the current TACACS+ action. However, when the system was setting the server abort string to send to the server, the specified string was longer than the limit. The code detected this and robustly truncated the string to an acceptable length.
RECOMMENDED ACTION: Report this to the TAC as a low priority defect to resolve. This will not cause any system problems as the code has detected the problem and robustly accounted for it.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SVR_LIST

SEVERITY: Error
FORMAT: Destination only has %d entries, needs %d. List is truncated
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The routine that is to return a sored list of servers has detected that the destination is not large enough to store all of the configured servers. So it has truncated the list to what will fit.
RECOMMENDED ACTION: Contact the TAC for logging a defect.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_SVR_END

SEVERITY: Error
FORMAT: The server list did not end when expected.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: While traversing the server list a sanity check is done to ensure we do not loop too many times. We hae detected that we were attempting to loop too many times so the loop was terminated and this error logged. It is possible that this issue is occuring because the AAA server linked list has become corrupted
RECOMMENDED ACTION: If this problem occurs frequently then the following work arounds can be applied: - if on standby PXM, reset it. - if on active PXM of redundant system then do a switch over. - if problem persists after switchover, then reset the standby, and immediately reset the active so the entire system rebuilds. - if on active PXM of non-redundant system, then reset the active PXM. - if none of the above works, then contact the TAC for help with correcting the problem.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-7-NETWORK_DOWN

SEVERITY: Information
FORMAT: Network interface down. Falling back to next configured authentication/authorization method.
FLAG: No Flag
THROTTLING: Five minutes
EXPLANATION: The internal interface to the network is down. This happens regularly when the user attempts to log on before stage 4 task initialiation completes (such as when the prompt shows the status of 'ia' or 'if') and remote authentication or authorization has been enabled. The AAA mechanism will fall back to the next configured method, local or cisco. Note this is only logged once every 5 minutes but could occur multiple times during that period.
RECOMMENDED ACTION: Wait until the system has fully initialized and log in then.
REQUIRED INFO: No Required Info

AAA-4-IE_SOCKET

SEVERITY: Error
FORMAT: %.40s failed for %d.%d.%d.%d/%d. errno:0x%x
FLAG: Stack Trace
THROTTLING: Five minutes
EXPLANATION: Internal Error A system call related to obtaining and or configuring a socket connection failed for AAA. Note this is only logged once every 5 minutes but could occur multiple times during that period. Statistics for these failures are kept and visible via the shellconn command aaaShowSocketStats
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_INVALID_PTR

SEVERITY: Error
FORMAT: Invalid pointer parameter received. Pointer %.40s, address:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: Sanity checks have determined that the errored function has received an invalid pointer (NULL, missaligned or pointing to an invalid region). Each case is different, and therefore we cannot give specific details regarding the cause and impact of this issue. In general the system will robustly detect this and move on accordingly.
RECOMMENDED ACTION: If this issue occurs frequently for: - the standby PXM, reset it. - the active PXM of a redundant PXM configuration, then do a switch over. - the active PXM of a single PXM configuration, then reset it.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_BUFF_P

SEVERITY: Error
FORMAT: Non-null buffer pointer 0x%x.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: During sanity checks we found that the transmit/receive buffer had a non-null value when it was expected to be NULL. In order to complete the current action, the pointer was set to NULL and we procced as expected. We cannot free the memory pointed to by this pointer because we do not know if this it is really dynamically allocated or not, and if it is, we do not know if we own it. Consequently there MIGHT be a memory leak here.
RECOMMENDED ACTION: This error will not break AAA functionality, but it has detected an unexpected situation. Please contact the tAC to have a defect opened to resolve this issue. If there are 10 or more occurrences of this issue then be sure that the TAC is contacted for investigation of a potential memory leak.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_DUP_TID

SEVERITY: Error
FORMAT: Pslot:%d, TID:0x%x has resources already, freeing them
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When starting a TACACS+ action, we do a sanity check to ensure that the current task does not have any TACACS+ resources allocated -- we're just starting so there shouldn't be any yet. However, the sanity check found some resources, so we free them and proceed.
RECOMMENDED ACTION: This error robustly detected and corrected the problem. However, this really should not occur at all. Please collect the required information and contact the TAC to have a defect opened to resolve this issue.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_WRONG_TASK

SEVERITY: Error
FORMAT: func:%.40s invoked from %.40s, only suppose to be invoked from tAAAsub
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: One of the important AAA subsystems such as disk writting or standby RAM syncing has been triggered by a task other than the AAA subtask. This could lead to unexpected results, due to possible write and update race conditions.
RECOMMENDED ACTION: Collect the required information, and contact the TAC support team
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_TASK_EVT_REG

SEVERITY: Error
FORMAT: CTC event registration failed. f():%.40s errno:0x%x
FLAG: Stack Trace | Write to BRAM
THROTTLING: One Tick
EXPLANATION: Internal Error: While the tAAA task was attempting to come up and initialize, it registers to receive CTC events. This registration failed, so the tAAA task could not come up. The Controller Card (CC) will go through its robust mechanism, which is to reset itself. If the problem does not clear itself with the reset then the CC will come up in failed state. When a CC comes up in the failed state, login access is restricted to the cisco user via the console port. Refer to the errno as well as other event and error logs to determine the exact failure.
RECOMMENDED ACTION: There is no recommended action for this as the MGX will go through its robust mechanism, which is to reset itself a few time to try and clear the issue. If it cannot clear the issue then the card will come up in the failed state.
REQUIRED INFO: Please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod CTC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - dsperrhist - sh> logConsoleShow (This needs to be done right after the card has reset so we can observer the boot up information). - sh> shmCsmTraceShow <failed CC's slot> - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_BAD_CTC_SLOT

SEVERITY: Error
FORMAT: Invalid slot (%d) from CTC event. errno:0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When a card is removed, a message is sent by the Card Task Controller to the tAAA handler which then ensures that no TACACS+ resources are allocated for the card that was just removed. However, we could not determine the slot from the incomming message. Consequently it is possible that we have a TACACCS+ resource leak. Typically you will not notice an AAA resource leak, as the system is designed to handle the maximum of all 32 telnet session (16 active, at standby) and all 8 FTP sessions (4 active, 4 standby) simultaneously. However, if enough resources have leaked you would eventually start to see IE_CTX_UNAVAIL or IE_CON_UNAVAIL errors. In any case, we would fall back to the next configured AAA method.
RECOMMENDED ACTION: If you have a redundant PXM then a switch over will clean up any possible AAA resource leaks that might have been caused by this problem. If you have a single PXM, then you will not see this issue because it only occurs on redudant PXM configuration.
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod CTC - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-5-W_EARLY_FAIL

SEVERITY: Warning
FORMAT: Early fail response received from ACS %d.%d.%d.%d/%d for user '%.16s'
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: TACACS+ Server Error: Typically an authentication failure is expected after the username and password have been sent to the server. However, we have received a fail response before that. This could imply that the server and the MGX are having problems communicating with each other, and their configurations should be checked.
RECOMMENDED ACTION: First, validate that the encryption key on the server and the MGX match. If they match, then tat is not the problem so refer to the server's error logs to determine why it was sending a premature fail message, and correct the configuration change accordingly.
REQUIRED INFO: No Required Info

AAA-5-W_EARLY_PASS

SEVERITY: Warning
FORMAT: Early pass response received from ACS %d.%d.%d.%d/%d for user '%.16s'
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: TACACS+ Server Error: Some servers allow the administrator to configure a user such that they do not need to enter a password. Only the username is needed. This is functionality that the MGX has purposely choosen to disregard for security reasons. During user authentication, the MGX received a pass response from the server before the username and password have been obtained and authenticated from the user.
RECOMMENDED ACTION: Reconfigure the server so that the user requires a password
REQUIRED INFO: No Required Info

AAA-4-IE_BAD_RSPID

SEVERITY: Error
FORMAT: Invalid respond id for command 0x%x, with status 0x%x
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: The function was attempting to respond to a communication response id that wasn't set
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions where being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_AAACC_SIZE

SEVERITY: Error
FORMAT: CC data for AAA has unexpected size %d. Expected %d
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When we [cc] to the standby PXM, the [cc] message contains some AAA initialization information so the standby's session will behave the same as the active's session. However, a sanity check was done and it was found that the data sent was not of the expected size. This error is logged and the standby will now initialize itself by 'discovering' the AAA settings. Since the AAA settings may have been modified after this session was started, it then means that the standby will be using the current AAA settings rather than the settings established when the user first logged on. These current settings will only be used while [cc]ing to the standby, when they go back to the active PXM, the old established settings will be used on the active.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions were being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-4-IE_AAACC_VERSN

SEVERITY: Error
FORMAT: Unexpected version (%d) for AAA data in CC message
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: Internal Error: When we [cc] to the standby PXM, the [cc] message contains some AAA initialization information so the standby's session will behave the same as the active's session. However, a sanity check was done and it was found that the data sent was not of the expected version. This error is logged and the standby will now initialize itself by 'discovering' the AAA settings. Since the AAA settings may have been modified after this session was started, it then means that the standby will be using the current AAA settings rather than the settings established when the user first logged on. These current settings will only be used while [cc]ing to the standby, when they go back to the active PXM, the old established settings will be used on the active.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: Before applying the recommended workaround, please collect the following information, and be sure to provide a detailed accounting of what was occuring on the node at the time. These issues are done in response to CLI commands, and therefore do not occur all by themselves. Please provide a detailed accounting of what CLI or FTP related actions were being done on the switch. Please collect the following information: - dspcds - dsprevs - dspaaa - dspaaa-stats detail - dsplog -mod AAA - dsplog -task tAAA - dsplog -task tAAAsub - dsplog (showing entries a few minutes before and after the AAA related events). - dsperrs - dsperr for the specific case - sh> aaaShowAll (warning this is a very large screen dump for nearly all pieces of information. We need ALL of this information please.)

AAA-5-W_NO_STAT_SEND

SEVERITY: Warning
FORMAT: AAA stats are not sent to active PXM during an upgrade.
FLAG: No Flag
THROTTLING: Thirty minutes
EXPLANATION: Some action was done on the standby PXM that would normally cause AAA statistics to be updated. However, we have detected that we are in the middle of an upgrade, in which case we do not send the statistics update message. This event warns us that this has occured.
RECOMMENDED ACTION: Complete the upgrade, after which the standby AAA activities will update the AAA stats stored on the active.
REQUIRED INFO: No Required Info

AAA-5-W_THROTTLED

SEVERITY: Warning
FORMAT: Method fallback due to network buffer throttling. size:%d limit:%d free:%d
FLAG: No Flag
THROTTLING: Thirty minutes
EXPLANATION: System Limitation: AAA code has detected that the system buffers used for TCP connections, as well as other system actions, has been depleted beyond the AAA usage threshold. Consequently this warning is logged and the AAA action will fall back to the next configured authentication or authorization method. This is just a warning message that the pool is below AAA's acceptable usage threshold. This might be caused by excessive AAA activity as explained below as well as in the Recommended Actions section, or it might be that some other application has drained the system buffer pools (as observed via the shellconn command netStackSysPoolShow.) This throttling has been put into place to ensure that AAA does not cause the system buffer pools to become completely exhausted. The user can do some investigation and if this throttling is found to be caused by AAA, the user can then reconfigure the switch and/or their scripts to avoid this. Refer to the recommended action section. One example of how this throttling threshold might be reached by AAA, is by having an extremely high rate of socket open and close actions. Such as when TACACS+ command mode authorization is enabled, the server is configured for multi connect mode (i.e. the servers -single option is false), and a script is running without sufficient delay between command invocations. Under this configuration, every single command executed will attempt to open a TCP connection to the switch, request authorization, and then close the connection once the authorization response has been received. However, due to an operating system limitation when the the TCP connection is closed, the socket lingers for awhile, keeping its resources. If we continually hammer the switch with commands, it could cause us to run out of system resources, because we are consuming resources at a rate faster than they are freed. While, the switch can handle normal manual CLI usage, however, it can become overloaded when scripts are running and the scripts do not have a sufficient delay between the commands being executed. This warning is saying that we are attempting to do command mode authorization and we have detected that the system buffer pools are below the AAA threshold. Rather than allowing a resource depletion we have throttled the command authorization throughput, falling back to the next configured authorization method.
RECOMMENDED ACTION: First you need to determine if this issue is being caused by command mode authorization for scripts or not. If it is then you can apply one of the work arounds listed below. Ultimately the user must determine who was logged on when the warning was issued, and if those logins where executing scripts. If there where scripts running at the time, then this is most likely caused by insufficient delay between command invocation.
1. If this warning was found to be be caused by scripts, then they need to be updated to have sufficient delay between command invocation. Determining the correct delay value for the scripts requires a bit of fine tunning, because the amount of delay between command invocation is dependant upon the number of scripts that will be run simultaneously. Tests where done with up to 8 simultaneous scripts running and the command throughput is approximately 1 command per .6 seconds. (i.e. if one script is running the delay between commands should be .6 seconds; if two scripts are running simultaneously, then the delay should be 1.2; if 3, then 1.8; if 4 scripts then 2.4 seconds; if 8 simultaneous scripts then 5 seconds, etc.)
2. Another options, the preferred option, is to change the MGX's AAA server configuration to communicate with the server using single connect mode. However this requres that the server supports this connect mode.
REQUIRED INFO: No Required Info

AAA-4-IERR_INV_NETPTR

SEVERITY: Error
FORMAT: Invalid network buffer pool pointer.
FLAG: No Flag
THROTTLING: Thirty minutes
EXPLANATION: Internal Error: An AAA command mode authorization attempt was being made, and the code was trying to check the the system resource usage to ensure that the AAA process does not consume too many resources. However, the AAA process detected that the global system network pool buffer pointer, _pNetSysPool, was invalid. Consequently all AAA command mode authorization actions will be throttled, meaning we fall back to the next configured method.
RECOMMENDED ACTION: Contact the appropriate support personnel for logging a defect. A system global has become corrupted, and the event needs to be investigated on a case by case basis. A possible work around for this situation would be a processor card switch over, or rebuild.
REQUIRED INFO: No Required Info

AAA-4-IERR_INV_MSGIDX

SEVERITY: Error
FORMAT: Invalid %.10s message index old:%d/new:%d should be (%d) or less.
FLAG: Stack Trace
THROTTLING: One minute
EXPLANATION: Internal Error: AAA validates message indices when it manipulates or accesses messages for AAA statitics. In this case the code found that the specified index was too large. The code logs this error, and then corrects the index. The end result is that some AAA statistic messages may be lost.
RECOMMENDED ACTION: This problem cannot be worked around, it is indicative of a coding defect which will need to be logged.

DDTS: ANN

ANN-4-MODERR

SEVERITY: Error
FORMAT: Ann Module Error: %s %d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Announcemnt module internal error occured.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect dsplog, dsperr, dspanncontrols, dspannfiles information

ANN-4-ERRMSG

SEVERITY: Error
FORMAT: Ann Module Error Message: %s
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Announcemnt module internal error occured
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect dsplog, dsperr, dspanncontrols, dspannfiles information

ANN-4-INV_PARAM

SEVERITY: Error
FORMAT: Ann Module Input Error: %s (%d)
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect dsplog, dsperr, dspanncontrols, dspannfiles information

ANN-4-INV_PARAMX

SEVERITY: Error
FORMAT: Ann Module Input Error: %s (0x%x)
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: API Software Error. The parameter value for the named parameter passed in as an argument to the named function was invalid.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect dsplog, dsperr, dspanncontrols, dspannfiles information

ANN-4-SWERR

SEVERITY: Error
FORMAT: Ann Module SW error: %s, 0x%x, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Announcement module miscellaneous software error occurred.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect dsplog, dsperr, dspanncontrols, dspannfiles information

ANN-6-INFOLOG

SEVERITY: Notice
FORMAT: ANNOUNCEMENT INFO LOG: %s %d.\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Miscellaneous software events occurred.
RECOMMENDED ACTION: No Action required
REQUIRED INFO: No Required Info

ANN-4-GENERR

SEVERITY: Error
FORMAT: ANNOUNCEMENT:: %s Error: 0x%x, 0x%x, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Announcement Module Error as depicted in event log occurred.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: Collect dsplog, dsperr, dspanncontrols, dspannfiles information

DDTS: ars

ARS-5-ARSERR

SEVERITY: Warning
FORMAT: ARS Error: %s
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

ARS-4-GENERR

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

DDTS: BCDRV

BCDR-5-DRVERR

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

BCDR-4-ERRMSG

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

BCDR-4-INV_PARAM

SEVERITY: Error
FORMAT: BCDRV Param Error: %s (%d)
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

BCDR-4-INV_PARAMX

SEVERITY: Error
FORMAT: BCDRV Param Error: %s (0x%x)
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

BCDR-4-SWERR

SEVERITY: Error
FORMAT: SW error: %s, 0x%x, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Miscellaneous software error occurred.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

BCDR-6-INFOLOG

SEVERITY: Notice
FORMAT: BCDRV INFO LOG: %s %d.\n
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

BCDR-4-GENERR

SEVERITY: Error
FORMAT: %s Error: 0x%x, 0x%x, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Error as depicted in event log occurred.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

BCDR-6-TRANSTYPE

SEVERITY: Notice
FORMAT: %s %d: %s \n
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: CDMON

CDMO-5-CDMONERR

SEVERITY: Warning
FORMAT: CDMON Error: %s
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CDMO-4-IPCSENDFAIL

SEVERITY: Error
FORMAT: %s, line %d: Ipc send fail in %s
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Internal software error.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: - On PXM45:
1. dspver
2. dspdate
3. dsplog -sl <slot that experienced this err>
4. dspcd <slot that experienced err>
5. dsperr <slot that experienced err>

CDMO-4-IPCERR

SEVERITY: Error
FORMAT: IPC failure: Error 0x%x, %s, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Error occurred while making IPC function call. This event log is usually accompanied by a corresponding IPC event log.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

CDMO-4-SWERR

SEVERITY: Error
FORMAT: SW error: Error 0x%x, %s, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Miscellaneous software error occurred.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only)

CDMO-2-TASKINIT

SEVERITY: Major Alert
FORMAT: ERROR 0x%x: CDMON task initialization failure
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Error occurred during CDMON task initialization. The error is fatal if it prevents the VXSM from going to the card ready state. When this happens, VXSM gets reset.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
If VXSM does eventually come up, on VXSM:
1. dspcd
Note whether event is logged during to card reset .

CDMO-2-DSPMISMATCH

SEVERITY: Major Alert
FORMAT: Numbers of DSP on active card (has %d DSP) and standby card (has %d DSP) are mismatched: need to replace the hardware
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Error occurred during CDMON task initialization. When this happens, VXSM gets reset.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO:

CDMO-6-INFOLOG

SEVERITY: Notice
FORMAT: CDMON INFO LOG: %s %d.\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Miscellaneous software error occurred.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
On VXSM:
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only)

CDMO-4-GENERR

SEVERITY: Error
FORMAT: %s error: Error 0x%x, %s, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Error as depicted in event log occurred.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
On VXSM:
1. dspcd
2. dspver
3. dsplns
4. dspports
5. dspparts
6. dspapslns (SONET cards only)

DDTS: snmp-ma

CB_S-5-MSGSENDFAILWARN

SEVERITY: Warning
FORMAT: snmpSendToRpm(slot %d, ptr 0x%x len=%d) failed.
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: Attempt to send a control point message to RPM card failed.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: On PXM:
1. dspcds
2. dsplog
3. dsperr
4. dsprev
5. memshow

DDTS: signaling

CC-5-CC_PB_QUEUE_WAR

SEVERITY: Warning
FORMAT: CC PB Queueing Looped Connection Func:%s ConnType:%s IfId:%d Vpi:%d Vci:%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Priority bumping warning, Please See the format string of this event for detailed explanation
RECOMMENDED ACTION: Check if looped connection is valid
REQUIRED INFO: If looped connections is not valid then gather information regarding connection, topology information ie. reachable address (local and network), dsppnni-path etc.

DDTS: VXSM_CCM

VXSM-4-CCMERR

SEVERITY: Error
FORMAT: CCM Error: %s
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Internal software error.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: - On PXM45:
1. dspver
2. dspdate
3. dsplog -sl <slot that experienced this err>
4. dspcd <slot that experienced err>
5. dsperr <slot that experienced err>

VXSM-4-IPCSENDFAIL

SEVERITY: Error
FORMAT: %s, line %d: Ipc send fail in %s
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Internal software error.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: - On PXM45:
1. dspver
2. dspdate
3. dsplog -sl <slot that experienced this err>
4. dspcd <slot that experienced err>
5. dsperr <slot that experienced err>

VXSM-4-IPCERR

SEVERITY: Error
FORMAT: IPC failure: Error %s, %d, %d\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Error occurred while making IPC function call.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-SWERR

SEVERITY: Error
FORMAT: SW error: Error 0x%x, %s, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Miscellaneous software error occurred.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-MEMLOWERR

SEVERITY: Error
FORMAT: Memory Low error: %s \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Memory Low Software Error Event occurred.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver
3. dsplns

VXSM-4-MEMHIGH

SEVERITY: Error
FORMAT: Memory High event: %s \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Memory High Event occurred.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver
3. dsplns

VXSM-4-IPCBUFLOWERR

SEVERITY: Error
FORMAT: IPC Buffers Low: Error %s\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: IPC Buffers Low Event error occurred.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-IPCBUFHIGH

SEVERITY: Error
FORMAT: IPC Buffers High %s\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: IPC Buffers High Event occurred.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-PEAKCPUHIGHERR

SEVERITY: Error
FORMAT: CPU High Utilization Error: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: CPU Utilization is above high water mark.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-PEAKCPULOW

SEVERITY: Error
FORMAT: CPU Low Utilization: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: CPU Utilization is below low water mark.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-PEAKCPUMEDERR

SEVERITY: Error
FORMAT: CPU Medium Utilization Warning: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: CPU Utilization is above medium water mark.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-AVGCPUHIGHERR

SEVERITY: Error
FORMAT: Average CPU High Utilization Error: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: CPU Utilization is above high water mark.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-AVGCPULOW

SEVERITY: Error
FORMAT: Average CPU Low Utilization: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: CPU Utilization is below low water mark.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-AVGCPUMEDERR

SEVERITY: Error
FORMAT: Average CPU Medium Utilization Warning: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: CPU Utilization is above medium water mark.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-2-TASKINIT

SEVERITY: Major Alert
FORMAT: ERROR: CCM task spawn failure %s
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Error occurred during CDMON task initialization. The error is fatal if it prevents the VXSM from going to the card ready state. When this happens, VXSM gets reset.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
If VXSM does eventually come up, on VXSM:
1. dspcd
Note whether event is logged during to card reset .

VXSM-2-TASKUTILHIGH

SEVERITY: Major Alert
FORMAT: Task utilization high error: %s, %d
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: One of the tasks takes up considerable CPU time.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
If VXSM does eventually come up, on VXSM:
1. dspcd
Note whether event is logged during to card reset .

VXSM-6-LOG

SEVERITY: Notice
FORMAT: CDMON LOG: %s, %d, %ld, %ld\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Miscellaneous software error occurred needs to be logged.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
On VXSM:
1. dspcd
2. dspver
3. dsplns

VXSM-4-GENERR

SEVERITY: Error
FORMAT: Error: %s \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Error as depicted in event log occurred.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
On VXSM:
1. dspcd
2. dspver
3. dsplns

VXSM-4-MSGQLOW

SEVERITY: Error
FORMAT: Message Queue Low Utilization: %d\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Message Queue Low Event error occurred.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-MSGQHIGHERR

SEVERITY: Error
FORMAT: Message Queue High Utilization Error: %d\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Message Queue High Event occurred.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-HSSHIGHERR

SEVERITY: Error
FORMAT: HSS SEV3 Congestion: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: HSS memory pool unavailability: critical.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-HSSLOWERR

SEVERITY: Error
FORMAT: HSS SEV1 Congestion: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: HSS memory pool unavailability: low.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-HSSMEDERR

SEVERITY: Error
FORMAT: HSS SEV2 Congestion:: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: HSS memory pool unavailability: medium.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-SVCHIGHERR

SEVERITY: Error
FORMAT: SVC SEV3 Congestion: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: SVC memory pool unavailability: critical.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-SVCLOWERR

SEVERITY: Error
FORMAT: SVC SEV1 Congestion: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: SVC memory pool unavailability: low.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

VXSM-4-SVCMEDERR

SEVERITY: Error
FORMAT: SVC SEV2 Congestion:: %d \n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: SVC memory pool unavailability: medium.
RECOMMENDED ACTION: Please collect the following info and contact TAC.
REQUIRED INFO: On PXM45:
1. dspcds
2. dspcd <slot that experienced the error>
3. dsplog -sl <slot that experienced the error>
4. dsplog -sl <other slot in the pair if redundancy is configured>
5. dsperr for slots specified above.
6. dspver
On VXSM:
1. dspcd
2. dspver

DDTS: ccm

CCM-5-LOG_WARNING

SEVERITY: Warning
FORMAT: CCM/%s, %s, type=%d, intf=%d, st=%d\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Warning message to be logged
RECOMMENDED ACTION: No action required
REQUIRED INFO: No information is required.

DDTS: AAA

CLF-4-APPEND_INV_PTR2

SEVERITY: Error
FORMAT: One or more pointers is invalid: p1=0x%x, p2=0x%x.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: This error is logged when the application attempts to append an entry to a designated circular log file, and one or more pointers passed to the append routine is invalid.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: 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.

CLF-4-INIT_INV_PTR4

SEVERITY: Error
FORMAT: One or more ptrs is invalid: p1=0x%x, p2=0x%x, p3=0x%x, p4=0x%x.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: This error is logged when the application attemps to intialize the circular log control data structure, and one or more pointers passed to the initialization routine is invalid.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: 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.

CLF-5-FILE_CREATE_ERR

SEVERITY: Warning
FORMAT: cirLogFileCtl=0x%x, filename=%s, ioDesc=%d, errno=0x%x.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This warning is logged when the circular log file utility fails to create the circular log information file or the circular log file.
RECOMMENDED ACTION: If error is unlikely to happen. If it happens, it is probably because the disk is full or the designated directory is missing. If the warning happens because of insufficient disk space, the circular log utility will stop logging the warning when more disk space is available. If the warning happens because the directory that contains the circular log file is missing, the circular log utility will correct the problem without any user intervention.
REQUIRED INFO: No Required Info

CLF-5-IFILE_WRITE_ERR

SEVERITY: Warning
FORMAT: cirLogFileCtl=0x%x fileName=%s logFileNum=%d.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This warning is logged when the circular log utility fails to write to the circular log information file. The utility will attempt to correct the problem itself. No user intervention is required unless other circular log errors are logged at the same time.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CLF-4-DIV_BY_ZERO

SEVERITY: Error
FORMAT: cirLFCtl=0x%x cirLName=%s cirLSz=%d cirLEntSz=%d.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: The circular log utility attempts to determine the approximate number of entries in the most current circular log file by dividing the circular log file size with the predefined circular log entry size stored in the control data structure. However, the entry size is found to be zero.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: 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.

CLF-5-APPEND_ERR

SEVERITY: Warning
FORMAT: cLFCtl=0x%x, entN=%d, entLen=%d, ent=%.45s.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This warning is logged when the circular log utility failed to append an entry to the circular log file specified. This is most likely due to insufficient hard disk space or other hard disk errors.
RECOMMENDED ACTION: Look for hard disk errors in the event log to determine the cause of the warning. The warning will stop as soon as the hard disk problem is fixed.
REQUIRED INFO: No Required Info

CLF-4-INV_LENGTH

SEVERITY: Error
FORMAT: Len of str (first 10 chars = %-.10s) is %d. Max len allowed is %d.
FLAG: Stack Trace
THROTTLING: One Tick
EXPLANATION: This error is logged during circular log initialization. The application has used an invalid string to name the log directory, the log file, or the log information file.
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log. Issue the 'dsperr' command from the PXM to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the 'dsperr' output, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: 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.

CLF-7-LDIR_CREATED

SEVERITY: Information
FORMAT: New circular log directory created: %s.
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: A new circular log directory has been created.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CLF-7-FILE_CREATED

SEVERITY: Information
FORMAT: New circular log file or information file created: %s.
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: A new circular log file or information file has been created.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: CLI

CLI-7-CLISSHLOG

SEVERITY: Information
FORMAT: cliSsh: client@%s: %s
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: A ssh session was attempted by the user.
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

CLI-4-CLISSHERR

SEVERITY: Error
FORMAT: cliSsh: caller 0x%x, %s
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: An error occurred in SSH cli. The caller
RECOMMENDED ACTION: No action required
REQUIRED INFO: Please capture information related to this error dsplog commands.

CLI-5-SESNPURGE

SEVERITY: Warning
FORMAT: %s: %s %d of the %d %s %d
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: This event will be used to reflect success/failure status of the Server/Client sessions purging processes
RECOMMENDED ACTION: No action required
REQUIRED INFO: No Required Info

CLI-7-GENERR

SEVERITY: Information
FORMAT: Line %d: errno 0x%x: msg %s
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Reports a CLI general info
RECOMMENDED ACTION: Copy the error message exactly as it appears in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REQUIRED INFO: 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.

CLI-4-SHELLCONN_AMBIG

SEVERITY: Error
FORMAT: Attempting to register command %s whose abbreviation makes 'sh' (shellconn) ambiguous.
FLAG: Stack Trace
THROTTLING: No Throttling
EXPLANATION: The abbreviation 'sh' is reserved for shellconn, as is 'she', 'shel', etc. By CLI coding standards new commands should start with add, clr, cnf, dbg, del, dsp, set and tst. Moreover, the abbreviation 'sh' is used by TACACS+ authorization code to detect when [cc] sessions have entered shellconn, and must therefore uniquely identify shellconn. This is a sanity test that is done when commands are register in the system, to immediately identify coding problems.
RECOMMENDED ACTION: Log a defect
REQUIRED INFO: The dump from this error, noting the card type that this problem occured on.

CLI-4-CC_BUFFER_SMALL

SEVERITY: Error
FORMAT: CC buffer too small. Size:%d, Need:%d. Trying to add %.20s
FLAG: Stack Trace
THROTTLING: No Throttling
EXPLANATION: The MGX did a sanity check while creating the cc message, needed to share information for the cc session and found that the static buffer provided is not large enough to hold the data we need to transmit. Consequently the cc action is terminated.
RECOMMENDED ACTION: Log a defect
REQUIRED INFO: The dump from this error, as well as dsplog.

DDTS: clocking

CLK_-7-SSI_API_FAILED

SEVERITY: Information
FORMAT: SSI INFO: %s
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The Clock Task Called a SSI API that failed
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: CLKDRV

CLKD-4-DRVERR

SEVERITY: Error
FORMAT: CLKDRV Error: %s %d
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CLKD-4-ERRMSG

SEVERITY: Error
FORMAT: CLKDRV Error Message: %s
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CLKD-4-INV_PARAM

SEVERITY: Error
FORMAT: CLKDRV Param Error: %s (%d)
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CLKD-4-SWERR

SEVERITY: Error
FORMAT: SW error: %s, 0x%x, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Miscellaneous software error occurred.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CLKD-6-INFOLOG

SEVERITY: Notice
FORMAT: CLKDRV INFO LOG: %s %d.\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: No Explanation
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CLKD-4-GENERR

SEVERITY: Error
FORMAT: %s Error: 0x%x, 0x%x, 0x%x, 0x%x\n
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Error as depicted in event log occurred.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: ccma

CCMA-7-CCMAENTEREDTASK

SEVERITY: Information
FORMAT: Entered the cmRootTask Function
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is used for debugging only
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CCMA-7-CCMAAFTEREPID

SEVERITY: Information
FORMAT: This is for debugging
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is never used. Please ignore.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CCMA-7-CCMADEBUG1

SEVERITY: Information
FORMAT: This is for debugging
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is never used. Please ignore.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CCMA-7-CCMACHILDTASKSP

SEVERITY: Information
FORMAT: stacksize: %d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is never used. Please ignore.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CCMA-7-CCMATASKIDOFCHI

SEVERITY: Information
FORMAT: Task ID spawnwd is %d:
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is never used. Please ignore.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CCMA-7-CCMADEBUG4

SEVERITY: Information
FORMAT: This is for debugging
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is never used. Please ignore.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CCMA-7-CCMADEBUG5

SEVERITY: Information
FORMAT: This is for debugging
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is never used. Please ignore.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: COT

COT-2-MOD_INIT_FAIL

SEVERITY: Major Alert
FORMAT: COT-ERR: Init Failed for '%s' [Status %d, %s]
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Specified sub-module of COT failed to get initialized
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

COT-5-RES_ALLOC_FAIL

SEVERITY: Warning
FORMAT: COT-WARN: Resource [%s 0x%x] Allocation Failed [Status %d, %s]
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: Specified resource allocation failed
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

COT-5-RES_RELEASE_FAI

SEVERITY: Warning
FORMAT: COT-WARN: Resource [%s 0x%x] Release Failed [Status %d, %s]
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: Specified resource de-allocation/release failed
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

COT-4-NULL_POINTER_ER

SEVERITY: Error
FORMAT: COT-ERR: Pointer to '%s' is Null (Reference param1 0x%x, param2 0x%x)
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Pointer to the specific structure is NULL (should not be)
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

COT-5-UNSUP_FEATURE

SEVERITY: Warning
FORMAT: COT-ERR: Unsupported registry function called (Reference param1 0x%x, param2 0x%x)
FLAG: No Flag
THROTTLING: One Second
EXPLANATION: Call-Control invoked registry function not supported in COT/DIL
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

DDTS: cpro

CPRO-5-IRMHDDBCREATEFA

SEVERITY: Warning
FORMAT: Irm HDDB creation for vxsm cpro failed ret:%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: In the cpro irm init the HDDB creation failed, check for the return type and take check the function.
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-IRMHDDBCREATEOK

SEVERITY: Information
FORMAT: Irm HDDB creation for vxsm cpro is OK, ret:%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: In the cpro irm init function the creation of of HDDB is successful
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-5-IRMHDDBTBLCREAT

SEVERITY: Warning
FORMAT: Creation of HDDB table failed, ret:%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: In the CPRO of VXSM init function creation of table failed and the return value gives the reason for failure
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-5-IRMHDDBBWTBLCRE

SEVERITY: Warning
FORMAT: Creation of table for bandwidth storage failed ret:%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: In the vxsm cpro init function creation of bandwidth table failed, check the return value
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-5-IRMDBREGISTERFA

SEVERITY: Warning
FORMAT: IRM HDDB register failed in cpro module ret:%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: In the vxsm cpro module the irm init function failed to regsiter the HDDB and the reason is obtained by looking at the return value
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-IRMINITOK

SEVERITY: Information
FORMAT: IN CPRO IRM INIT IS OK
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The irm initialization is OK in in the vxsm cpro module
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-ENTEREDIRMHDDBC

SEVERITY: Information
FORMAT: Entered vxsm cpro call back
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Entered the cpro call back and if this event is not logged call back is not invoked
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-ENTEREDIRMHDDBC

SEVERITY: Information
FORMAT: Eneterd the addcon handler in the call back of vxsm cpro
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: The event is logged whenever the addcon call abck is invoked
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-ENTEREDIRMHDDBC

SEVERITY: Information
FORMAT: Entered the bulk sync in the call back
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPRODEBUG1

SEVERITY: Information
FORMAT: Before cProTaskInit
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPRODEBUG2

SEVERITY: Information
FORMAT: After cProTaskInit
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPRODEBUG3

SEVERITY: Information
FORMAT: Before epid of cpro
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPRODEBUG4

SEVERITY: Information
FORMAT: After epid of cpro
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPRODEBUG5

SEVERITY: Information
FORMAT: debug
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPRODEBUG6

SEVERITY: Information
FORMAT: debug
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPROHANDLECNFG

SEVERITY: Information
FORMAT: Channel config invoked
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the channel config is invoked
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPROADDCONN

SEVERITY: Information
FORMAT: ifnum:%d vpi:%d vci:%d
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPROSENDCNTRL

SEVERITY: Information
FORMAT: debug
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-7-CPROCNTRLACKREC

SEVERITY: Information
FORMAT: debug
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: This event is logged when the call back is invoked during bulk sync
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CPRO-4-BULK_EVENT_FOR_

SEVERITY: Error
FORMAT: %s; port = %u; array index = %u
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Received a bulk event on an invalid interface
RECOMMENDED ACTION: Pls collect the requested info and refer to the TAC details
REQUIRED INFO: From PXM card, collect:
1. dsprevs,
2. dsplog for that slot,
3. dsperr for that slot
From the MPSM/MXSM card, collect:
1. dsplns (both ATM & FR context),
2. dspports (both ATM & FR context),
3. dspcons & dspcon for connections on that port
4. dspprfhist.

CPRO-4-TRANS_ID_DB_UPD

SEVERITY: Error
FORMAT: Conn = (%d.%d.%d, rec# %d); ... Operation = %d; Error = %d;
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Transaction Id Disk DB update on PXM Hard Disk failed
RECOMMENDED ACTION: This event is logged when a transaction id disk DB update on PXM
REQUIRED INFO: From PXM card, collect:
1. dsprevs,
2. dsplog for that slot,
3. dsperr for that slot,
4. dsppnports
From AXSM card, collect:
1. dspports,
2. dspcon for that connection,
3. dsplns

CPRO-4-DROP_VSI_EVENT

SEVERITY: Error
FORMAT: Dropped VSI event for conn (%u.%u.%u, rec# %u); event=%u; param1=%u; param2=%u; param3=%u
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: CPRO dropped a VSI event because of local error
RECOMMENDED ACTION: Pls collect the requested info and refer to the TAC details
REQUIRED INFO: From PXM card, collect:
1. dsprevs,
2. dsplog for that slot,
3. dsperr for that slot
From the MPSM/MXSM card, collect:
1. dsplns (both ATM & FR context),
2. dspports (both ATM & FR context),
3. dspcons & dspcon for connections on that port
4. dspprfhist.

CPRO-4-LICENSE_MGMT

SEVERITY: Error
FORMAT: %s; Conn ifNum=%u, dlci=%u, NumFrAbrConns=%u, NumLicenses=%u
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: License Management call fails
RECOMMENDED ACTION: Pls collect the requested info and refer to the TAC details
REQUIRED INFO: From PXM card, collect:
1. dsprevs,
2. dsplog for that slot,
3. dsperr for that slot
From the MPSM card, collect:
1. dspports (both ATM & FR context),
2. dspcons & dspcon for connections on that port
3. dspprfhist.

CPRO-4-LM_RESYNC_ERR

SEVERITY: Error
FORMAT: %s; OLD NumFrAbrConns=%u, NumLicenses=%u; NEW NumFrAbrConns=%u, NumLicenses=%u
FLAG: No Flag
THROTTLING: One Tick
EXPLANATION: Resync detected and corrected License Management db error
RECOMMENDED ACTION: Pls collect the requested info and refer to the TAC details
REQUIRED INFO: From PXM card, collect:
1. dsprevs,
2. dsplog for that slot,
3. dsperr for that slot
From the MPSM card, collect:
1. dspports (both ATM & FR context),
2. dspcons & dspcon for connections on that port
3. dspprfhist.

DDTS: CRML

CRML-2-MOD_INIT_FAIL

SEVERITY: Major Alert
FORMAT: CRML-ERR: %s: Init Failed for '%s' [Status %d, %s]
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Specified sub-module of CRML failed to get initialized
RECOMMENDED ACTION: Inform TAC immediately
REQUIRED INFO: If CLI is available, capture the following output before contacting TAC: dspcds, dsprevs, dsplog -sl <vxsmSlot>, dsperr -sl <vxsmSlot>, and dspver on the vxsmSlot

CRML-5-RES_ALLOC_FAIL

SEVERITY: Warning
FORMAT: CRML-WARN: Resource [%s] Allocation Failed [Status %d, %s]
FLAG: No Flag
THROTTLING: One minute
EXPLANATION: Specified resource allocation failed
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CRML-5-RES_RELEASE_FAI

SEVERITY: Warning
FORMAT: CRML-WARN: Resource [%s] Release Failed [Status %d, %s]
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: Specified resource de-allocation/release failed
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CRML-5-DSP_CHAN_MODIFY

SEVERITY: Warning
FORMAT: CRML-WARN: DSP [DSP # %d, Bearer Channel # %d] Modification Failed [Status %d, %s]
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: Internal software error
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CRML-2-REDM_ADDCON_FAI

SEVERITY: Major Alert
FORMAT: CRML-ERR: REDM: Could not Add %u Conn ds0(0x%x) pt/vpci(0x%x) status %x
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: Internal software error
RECOMMENDED ACTION: Reset the standby VXSM, and inform TAC if the problem recurs
REQUIRED INFO: If CLI is available, capture the following output before contacting TAC: dspcds, dsprevs, dsplog -sl <vxsmSlot>, dsperr -sl <vxsmSlot>, and dspver on the vxsmSlot

CRML-2-REDM_MODCON_FAI

SEVERITY: Major Alert
FORMAT: CRML-ERR: REDM: Could not Modify %u Conn ds0(0x%x) pt/vpci(0x%x) status %x
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: Internal software error
RECOMMENDED ACTION: Reset the standby VXSM, and inform TAC if the problem is recurring.
REQUIRED INFO: If CLI is available, capture the following output before contacting TAC: dspcds, dsprevs, dsplog -sl <vxsmSlot>, dsperr -sl <vxsmSlot>, and dspver on the vxsmSlot

CRML-2-REDM_DELCON_FAI

SEVERITY: Major Alert
FORMAT: CRML-ERR: REDM: Could not Delete %u Conn ds0(0x%x) port/vpci(0x%x) status %x
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: Internal software error
RECOMMENDED ACTION: Reset the standby VXSM, and inform TAC if the problem is recurring.
REQUIRED INFO: If CLI is available, capture the following output before contacting TAC: dspcds, dsprevs, dsplog -sl <vxsmSlot>, dsperr -sl <vxsmSlot>, and dspver on the vxsmSlot

CRML-5-DSP_CONGESTION_

SEVERITY: Warning
FORMAT: CRML-WARN: DSPRM: DSP State is now %s
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: DSP congestion state change indication
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CRML-4-NULL_POINTER_ER

SEVERITY: Error
FORMAT: CRML-ERR: %s: Pointer to '%s' is Null (Reference param1 0x%x, param2 0x%x)
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: Pointer to the specific structure is NULL (should not be)
RECOMMENDED ACTION: If this messages recurs, report it to your TAC.
REQUIRED INFO: If CLI is available, capture the following output before contacting TAC: dsprevs, dsplog -sl <vxsmSlot>, dsperr -sl <vxsmSlot>, and dspver on the vxsmSlot

CRML-4-DSP_CONFIG_PARA

SEVERITY: Error
FORMAT: CRML-ERR: SAPIL: Failed to configure DSP parameter %d with status %s (ccbPtr 0x%x, dspIntfPtr 0x%x)
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: DSP configuration for the specified parameter failed
RECOMMENDED ACTION: If this messages recurs, report it to your TAC.
REQUIRED INFO: If CLI is available, capture the following output before contacting TAC: dsprevs, dsplog -sl <vxsmSlot>, dsperr -sl <vxsmSlot>, and dspver on the vxsmSlot

CRML-5-UNSUP_FEATURE

SEVERITY: Warning
FORMAT: CRML-ERR: SAPIL: Unsupported registry function called (Reference param1 0x%x, param2 0x%x)
FLAG: No Flag
THROTTLING: One Hour
EXPLANATION: Call-Control invoked registry function not supported in CRML/DIL
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CRML-5-TOO_MANY_DIGITS

SEVERITY: Warning
FORMAT: CRML-ERR: SAPIL: Call-Control requested too many (%d) digits to dial. Max is %d. (dspIntfPtr 0x%x)
FLAG: No Flag
THROTTLING: One Minute
EXPLANATION: Call-Control requested more digits to be dialed than DIL supports
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CRML-5-REDM_DELCON_WAR

SEVERITY: Warning
FORMAT: CRML-Warning: REDM: Delete Recreation - %s ccbPtr=%p contype %u ep %u-%u
FLAG: No Flag
THROTTLING: No Throttling
EXPLANATION: Internal software error
RECOMMENDED ACTION: No Recommended Action
REQUIRED INFO: No Required Info

CRML-4-CM_DSPAPI_ERROR

SEVERITY: Error
FORMAT: CRML-ERR: DIL retruned error %s for transaction=%p on cmReqPtr=%p, ccbPtr=%p